Presagis

I was wondering if I’m overlooking any preferences for having the texture and external reference paths default to “relative” instead of “absolute.”  I can go into the list textures or list external references and click the relative button if they are not.  But iIs there a way to have that set as default (preferences or elsewhere), and if not could that be added to a future version feature wish list?

Another thing I would like to add to the future version feature wish list: have an option to have DOF always running.  Instead of having a flip-book animation running would like to have a check box for the DOF to be running by default.  Things like radar dishes, etc. would be nice not to have to send a control packet to turn the DOF on.  Just let it run from min to max at the step as specified in the DOF attribute window.  If constrain is unchecked it just keeps going…

Auto-animation of a DOF sounds more like a run-time implementation ..... Our IGs do it.

And it wouldbe nice to default to relative pathing, it’s all I use.  I have a droplet not on my desktop, drop a folder in and it paths everything to ../textures.  I wrote some scripts, too, that let you enter some exref pathing to out libraries and fixes them all by category.  Be a lot easier to check a box, though.

Would still like the always running DOF option.  Sometimes the models are not running on Presagis IG’s

Another thing I would like to add to the future version feature wish list: have an option to have DOF always running.  Instead of having a flip-book animation running would like to have a check box for the DOF to be running by default.  Things like radar dishes, etc. would be nice not to have to send a control packet to turn the DOF on.  Just let it run from min to max at the step as specified in the DOF attribute window.  If constrain is unchecked it just keeps going…

This would have to be an option… Editing in this mode would be very difficult
BTW, have you tried the Local-DOF>DOF Viewer?

I’m assuming Rich wants this functionality on the IG side, not the Creator side.  You wouldn’t want them running in creator by default, it would be distracting and as you point out - difficult to edit.

I think this would be a multi-stage, multi-discipline option
OpenFlight needs one extra tag added to a DOF bead record to pass the info that this DOF is an “always running” DOF, like a radar dish.
Creator needs to access that tag and handle setting it, perhaps a defalt of OFF, and if you want it to always run, you set it on.  Better backward compatibility
Then, an option in the Presagis IG - “Turn Off ON DOFs” in case for some reason you want to turn this option off and manually drive the RADAR dish or whatever.  Ya never know what people will try, but somebody will complain if you have this new function but can’t turn it off 8*)

But I think the first step is to add a tag to the DOF record in OpenFlight

Along with a “multi-range LOD” node.

I’m assuming Rich wants this functionality on the IG side, not the Creator side.  You wouldn’t want them running in creator by default, it would be distracting and as you point out - difficult to edit.

Of course… thanks for the clarification… duh

So what is wanted is a new OpenFlight DOF attribute indicating to the run time that the DOF “just goes”.