Yes, sounds are only possible together with triggered animations, since this was not possible using the official FSX SDK.
However, static sounds can of course be added using FS SDKs effects system.
I think this project has used static sounds for ambient noise as attached effects and used SODE to...
Updated to v0.6:
Support for the (optional) TargetSim node for the entire xml project.
Using the TargetSim node, you can specify that this xml is only used for a specific simulators. A use case would be to have non-PBR SimObjects display in sims prior P3Dv4 and PBR SimObjects in P3Dv4 and v5...
No, you just need to ensure the client objects are within 40km of the data probe.
I would even go as far as installing a data probe for a cluster of wind turbines and place it in the center. This will certainly ensure that 40km radius requirement.
No, SODE updates its bubble as you fly through...
Got them, thanks.
You sir found a bug! It was quite tricky to hunt this one down, since it was due to a special, uncommon use case of SODE: Placing multiple objects (wind turbines I guess) over a large area.
The problem was that while some of the objects were indeed within the SODE bubble of...
Sorry, I don't frequent this forum that often these days...
Could you zip those 312 xml files and PM the zip to me? I don't even need the models, just the xmls. I can then run the debug version of SODE on those files and see what could be wrong. Something about a SimObjects called "WEA"...
Very cool idea! Yes, this is how it works in Zurich for example with the gate lead-in lights.
Right now, this is not possible. But I have noted your suggestion and will look into it.
I think it is a limitation of FSX and how it handles those fallback paths.
More specifically, I think it does not support absolute paths, only relative. But I haven't found any info on this assumption in the official FS SDK, but when I once tested an absolute path, then the textures didn't show up.
As for a guide: Here's a tutorial for SODEPlacer -> https://sode.12bpilot.ch/?document=tutorials/vdgs-workflow
I highly recommend using a visual tool for placing the VDGS, setting them up manually (especially the stopline positions) is cumbersome.
Do you mean create your own VDGS models or just placements?
Own VDGS units, no. Each VDGS of the different manufacturers have some specialities which can't be handled by a generic script as for jetways. If there's need for other VDGS types, I'll expand the pack in a free update.
Updated to v0.5:
Support for placement of VDGS boxes if you have purchased the SODE VDGS Pack
Added support for manipulating the heading of a selected object using the mousewheel and key modifiers SHIFT, CTRL
Fixed several minor bugs
You need to attach the "No Crash" property to your model within your modelling tool of choice, using the FS SDKs "Attach Point Tool" (e.g. http://www.prepar3d.com/SDKv3/LearningCenter/modeling/using_modeling_tools.html#The%20Attach%20Tool )