Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
"splitting" a D3Pro program
|
I have a Residential project with an unusually large (to me) D3Pro program.
It's about twice the size of most D3Pro programs I run across, with a file-size just under 15 meg - most D3Pro programs I work with are between 5 and 10 meg. I think part of the problem is that it contains all local dimmers, and no centralized panels or modules. It currently has about 250 EX and Horizon dimmers/keypads, and they're considering adding more :-) The problem is that it has become quite tedious to manage. Simply opening the d3p file takes slightly longer than normal, but when the dealer's programmer sends me an archive, it takes a solid 5 to 10 minutes for it to open, and creating a new filename/version with "Save As" takes 30 to 45 minutes! Compile and load times are also a little slow, but not too much slower than a normal-sized program would be. The other programmer has about the same, or worse, experience when working with the program on his PC, so I think it's a file issue and not a PC issue. Anyway, I'm wondering if the program could be "split" into two or three separate programs, e.g., for specific areas. I know scenes can be made to traverse multiple processors, but will the same thing also work with multiple programs on a single processor? One concern I have, is would D3Pro be able to create a different tag for each program, and load them to separate slots? Has anyone done this, and confirm it works? Do you have any other pointers? Thanks in advance. |
|
Make it a simpl program, it will be substantially smaller and more efficient.? Crestron has ceased development on D3 quite some time ago, so it is a good idea to move away from it.? And yes, it is slow.? To address your question specifically, you can "split" the program and use intersystem communication, but it does become very manual at that point.? ?The IP for EISC is 127.0.0.2.?
|
|
15 meg is alot? Many of my D3 files are way more than that. Working on one now thats 55mb. Yea its a fairly large house but not monumentally large. But I have another recent one thats a NYC apartment with 9 or so rooms and lighting and shades and thats 28mb. Yea D3 is slow but Ive never seen a Save As take that long. Maybe 5-10 mins tops on large jobs. I have found that if you have alot of scenes in D3 that it slows things down alot. But no way I can think of splitting it up while using D3. Simpl would be your best bet but then that defeats the purpose of using D3. Do you have any UIs generated by D3 like ipad or phone? That would certainly add bloat to the bloat.?
|
|
1. My sources have told me that D3 is still a 'Live' product, though clearly It has ceased at least for the time being to get much-needed love (Home is their new girlfriend...)
2. Are you using "Global Lighting Scenes" vs. "Global Presets"?? I found out the hard way 10 years ago that the 'Lighting Scenes' were not engineered properly and if you were to use more than a handful, the program and system would in various ways, grind to a halt... We also saw this problem 5 years ago with a project that I was integrating, but another person was doing the D3. After weeks of trouble-shooting and having TS make us try everything, I looked at the program and saw 100+ Lighting Scenes. We went thru the arduous task of converting them all to Global Presets and the system has been trouble free since then... This may not be your total issue, but if you're using Lighting Scenes, that is definitely a Yuge part of it... FTR, my approach with D3 is to program 99% of all load control with Global Presets, and drop them on buttons as needed.? The only exceptions are direct, individual load control on a button - ex: A reading light... And yes, I think its time to 'Roll our own' lighting code as painful and difficult as that is... - HOME has too many limitations and lacks Shared Gateway (still after 6 years) - D3 clearly will not be updated like it needs, and even if it was it would still be total bloat-ware |
|
I didn't write the D3Pro program, but I occasionally need to add things to the RSD that were missed by the original programmer, or fix feedback issues, etc. I'm aware that re-writing it in Simpl is a solution, but that's not going to happen. I don't have the time, and they wouldn't want to pay for it if I did :-)
toggle quoted message
Show quoted text
I did notice there are a lot of Global Lighting Scenes and very few Global Presets, so I'll have them start there. However, the program seems to run okay - it's just the opening of archives and re-saving that are issues. Saving with the same filename is actually okay, but using Save As to create a different filename takes FOREVER. Thanks for the tips! --- On Saturday, November 13, 2021 at 11:53 AM, Chris Kangis wrote: |
|
FWIW, "Save As" operations in standard SimplWindows have been taking a looooong time for me recently as well.? Often, I have to right-click close SW and reopen it.? The file has been saved, but SW is doing something in the background after the save. On Sun, Nov 14, 2021 at 9:49 AM Tony Golden <mrgolden@...> wrote: I didn't write the D3Pro program, but I occasionally need to add things to the RSD that were missed by the original programmer, or fix feedback issues, etc.? I'm aware that re-writing it in Simpl is a solution, but that's not going to happen.? I don't have the time, and they wouldn't want to pay for it if I did :-) |
|
I've actually had that happen with Simpl, but only a couple of times within the last year. I'm sure it's probably related, but this one D3Pro program is WAY worse than any others I've tried.
toggle quoted message
Show quoted text
Thanks for the heads-up. --- On Sunday, November 14, 2021 at 9:54 AM, Phil Bridges wrote: |
to navigate to use esc to dismiss