we have a lot more than 200 visibility conditions set in our model - assuming this is in P3Dv4, you shouldn't be looking for a problem with "too many of them" at 200 or so. It's something else. Perhaps something with a skinned part?
are you an admin in this forum? If yes, please let me know who, because I don't know you. If not, please don't assume to know what's best for our bandwidth (yes, I am an admin here).
Hiding behind a screen and a keyboard sometimes causes us to be very impolite - downright...
as a nice way to keep this thread current, would you be kind enough to consider opening the source code up for others to see?
I am particularly interested in the part where XToMDL barfs when exporting MDLs for FSX with more than 65,535 vertices for a certain material... it would be...
I recall having a discussion with someone at ACES about this (Adrian? I forget) and the quote was that there is no partial rendering of the model as the savings would be negated by the need to calculate shadowing anyway.
Regardless of the reason though, reality is - the model is always being...
The simple answer is: "it's not doable in the VC".
The reason is what you suspected: The model is built in 3d, so it's not just a graphical representation of a flat surface (a 2d panel gauge) which you can replace simply by changing its rectangle coordinates. It's a fully rendered three...
I sent a message a while ago to enquiries, as well as to yourself... never got any replies to either.
Could you care to contact me directly at (lkalamaras) (at) (flightsimlabs) (dot) (com) ?
sleep() will cause the thread to pause - if that's inside a PRE_UPDATE or a PRE_DRAW (or anywhere in the same FS thread), the entire app will seem to pause and stutter.
What you need is a variable that checks time-passed, which you'll initialize when you flick the switch, and...
This is a great candidate for some learning here, especially in the use of Visual Studio debugging!
I strongly recommend that you set up the gauge in debug mode and put breakpoints where the values are set - that way, you can see who is at fault for setting the values to 0.0 etc.
weather is the one area where FS could have been improved in terms of the SDK - SimConnect provides cloud density but NOT cloud precipitation, so you can't accurately receive information that would correspond to what real-world instruments do.
If you want to approximate, though...
you could try having the user install the SP2 simconnect.msi, which exists (once the SP2 SDK is installed) in
Core Utilities Kit\SimConnect SD\lib
that should fix any SxS discrepancies (provided that FSX SP2 *has* been installed correctly).
You *cannot* include this installer with...