Milton_Shupe
Resource contributor
- Messages
- 331
- Country
In FS9, modeled part names with suffixes ending with _### were treated as one part during the makemdl export/compile.
Therefore, I could have Pilot_01, Pilot_02, Pilot_03 and write custom visibility xml code using just "Pilot".
In FSX, that does not seem to work; the full name appears to need to match perfectly in spelling and case for xml to recognize it.
Do you know this to be the case?
In my HMS Bounty conversion to FSX project, I have running rigging, over 130 parts using 13 names with _## suffixes, as one example.
The visibility code is not working on these parts. They are not being recognized.
Is there a way in xml to simulate what I did in FS9 (or to get xtomdl to work same way to ignore the suffixes)?
For example, any name beginning with "pilot" will be subject to this visibility code.
This would then control parts named "Pilot_01, Pilot_02, and Pilot_03".
Thanks in advance for your ideas and insight.
Therefore, I could have Pilot_01, Pilot_02, Pilot_03 and write custom visibility xml code using just "Pilot".
In FSX, that does not seem to work; the full name appears to need to match perfectly in spelling and case for xml to recognize it.
Do you know this to be the case?
In my HMS Bounty conversion to FSX project, I have running rigging, over 130 parts using 13 names with _## suffixes, as one example.
The visibility code is not working on these parts. They are not being recognized.
Is there a way in xml to simulate what I did in FS9 (or to get xtomdl to work same way to ignore the suffixes)?
For example, any name beginning with "pilot" will be subject to this visibility code.
This would then control parts named "Pilot_01, Pilot_02, and Pilot_03".
Thanks in advance for your ideas and insight.
Last edited: