• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSX Prop_slow remains visible after adding a gauge

Kai503

Kai503

Messages
244
Country
finland
Hi Guys,

not sure where I should put this question, since it has a bit of everything..

prop0_still, prop0_slow and prop0_blur were tagged and everything was fine until now. I added a 3d gauge, added it to the modeldef and exported. The gauge is working, but since that the prop_slow is visible as long as the prop is turning.

What I tried:
-replaced the aircraft.cfg by a default one
-replaced the modeldef by an old one (without the gauge working)
-exported an older version of the plane
-replaced the prop_slow by an older one
-retagged the prop_slow

Nothing works, the prop_slow remains visible.

I'm at the end of my ideas. Does anyone have an idea?

Thanks!

Cheers,
Kai
 
My only guess is that you somehow replaced the prop_slow entry in the modeldef XML file in both copies you tried?
 
Check the User Properties for your prop0_slow to make sure you haven't lost the <Visibility> tag...
 
Thanks for the answers!

The visibility tag shows up in the User Properties and the prop_slow entry looks good in the modeldef..

What I tried now:
I made a very simple "test-plane". 3 boxes and tagged them with the 3 conditions. The slow and blurred boxes remained visible.
So the problem must be the modeldef. The second one I tried had custom entrys as well. It has been from my last project, where I haven't seen this problem. So I tried a complete "fresh" modeldef, and voilà, the prop works again as it should.
I added my fuel gauge back and even without tagging the needle I get the problem with the prop back.
Simply spoken; as soon as I change something in the modeldef I get the problem with the prop_slow.

Any ideas..?

Kai
 
I added my fuel gauge back and even without tagging the needle I get the problem with the prop back.
Click to expand...
Well, the answer is right there! Post your "fuel gauge" script and let's find out what is wrong with it... ;)
 
Hi,

Anything wrong with a part script at the top of the file will inactivate all part scripts below, as I understand it?
 
n4gix said:
Well, the answer is right there! Post your "fuel gauge" script and let's find out what is wrong with it... ;)
Click to expand...

I didn't post it yet, cause I thought it should be fine when the gauge is working as it should. But well, looks like I'm learning almost every day new mysteries about FSX.. :D

Here it is:
Code: 
<PartInfo>
 <Name>D8_Benzin_Uhr</Name>
 <AnimLength>100</AnimLength>
 <Animation>
  <Parameter>
   <Sim>
    <Variable>FUEL TANK CENTER LEVEL</Variable>
    <Units>percent</Units>
    <Scale>1</Scale>
   </Sim>
  </Parameter>
 </Animation>
</PartInfo>

Anything wrong with a part script at the top of the file will inactivate all part scripts below, as I understand it?
Click to expand...

That's interesting and good to know, Tom!

Kai
 
Hi,
hmm the code looks ok to me.

At the top of Modeldef.xml,did you insert an entry like the one you see below, but then with a unique guid and proper name etc?

<Animation name="wing_fold_r_pct" guid="571DC0FF-78AA-4aa7-BD64-AACAC2AA929C" length="100" type="Sim" typeParam2="wing_fold_r_pct" typeParam="AutoPlay" />

Hope this helps.

grt
Willem
 
Hi Willem,

thanks for the suggestion. Sure I have this entry as well, the GUID is made with GUID Gen, so it should be fine..

Kai

Btw. My Dutch girlfriend liked it when I told that a Dutch guy made a nice commend about my plane which was designed by a Dutch.. :D
 
Last edited:
I see nothing wrong either, but it is an absolute certainty that there is an error in the modeldef.xml somewhere, else it wouldn't kill the prop0_xxx visibility conditions!
 
Kai503 said:
Btw. My Dutch girlfriend liked it when I told that a Dutch guy made a nice commend about my plane which was designed by a Dutch.. :D
Click to expand...

:D it's a small world after all... you just gotta love Dutch aircraft, right?

Leuk! (Dutch for "Nice!")

Did you find the error yet?

grt
Willem
 
Hehe, yes, I love the Fokker planes. I got the chance to sit in a D.VII when I was 4 or 5 years old. That made for sure some imperssion on me and lasts until today. And of course, since some time I'm more often in The Netherlands and have been to Lelystad and so on. Ik vind het erg leuk (I hope it was right now..)

Unfortunately I haven't found the solution yet. As soon as I add the script to the new modeldef, I have the problem again. For now I use the default fuel indicator, which works perfectly. I got simply tired of trying and started to model the pilot. But I'll have to catch up the thing later again..

Cheers,
Kai
 
You must log in or register to reply here.
Back
Top