I downloaded R23 recently. I'm working with TNCM (Princess Juliana). I changed all that I needed to, did the error checking, fixed all the errors, but one doesn't go away. The helipad altitude always stays at like 0.12 F or something around that even though I put in the normal airport altitude in the altitude part. I've tried pressing enter after, saving right after, but no matter what when I click on the Helipad it always says like .12 F. I had just put the object lock on, but I took it off, tried again, same thing happened.
-
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.
Helipad Bug
- Thread starter Fleron230
- Start date
I am not able to duplicate this bug. I can change the altitude of the helipad to anything I want and it always get recorded properly.
Can you tell me what version of java you are using? (Open a command prompt and type java -version)
Also can you tell me exactly what steps you are taking when you are changing the helipad altitude?
Thanks!
-Russell
Can you tell me what version of java you are using? (Open a command prompt and type java -version)
Also can you tell me exactly what steps you are taking when you are changing the helipad altitude?
Thanks!
-Russell
I'm now using a different really old (498 MHZ IBM Processor) computer that can't support FSX, I was using a different computer before, so I'm not sure what Java I had on that one. I think that I had the newest type (because I downloaded Java just before R22), but I'm not sure.
Steps that I did:
1. Had everything already good, so I blocked everything
2. Did error checking, and got really high pattern and runway altitudes, and a small number altitude for the helipad
3.Unchecked helipad and runway
4.Changed the runway and pattern altitudes and it worked
5.Changed the Helipad into the exact altitude.
6.Did an error check and the helipad altitude showed up again
7.Put in normal altitude in helipad
8.Saved XML
9.Did error checking, still .12
10.Tried with a tiny bit higher number
11. Did error checking, still .12
And it went on like that , even though I was able to move the helipad. The helipad was also partly on an apron.
Steps that I did:
1. Had everything already good, so I blocked everything
2. Did error checking, and got really high pattern and runway altitudes, and a small number altitude for the helipad
3.Unchecked helipad and runway
4.Changed the runway and pattern altitudes and it worked
5.Changed the Helipad into the exact altitude.
6.Did an error check and the helipad altitude showed up again
7.Put in normal altitude in helipad
8.Saved XML
9.Did error checking, still .12
10.Tried with a tiny bit higher number
11. Did error checking, still .12
And it went on like that , even though I was able to move the helipad. The helipad was also partly on an apron.
Last edited:
Hi Russell,
I have been having repeated problems with Runway heights and Pattern Altitudes effectively doing their own thing, likewise Helipad heights. I get a build that works and then work on something like an apron. Come to do a build and error check to find that Runways are either at infinity or some other crazy value. Go in to correct runway height and the pattern height goes to pot. I have had to resort to editing the xml file and saving before re-opening in FSXP. Everything is fine for a while and then off it goes again.
For information I am using Java Hotspot(TM) Client VM (build 1.6.0_02-b05, mixed mode, sharing)
TonyM
I have been having repeated problems with Runway heights and Pattern Altitudes effectively doing their own thing, likewise Helipad heights. I get a build that works and then work on something like an apron. Come to do a build and error check to find that Runways are either at infinity or some other crazy value. Go in to correct runway height and the pattern height goes to pot. I have had to resort to editing the xml file and saving before re-opening in FSXP. Everything is fine for a while and then off it goes again.
For information I am using Java Hotspot(TM) Client VM (build 1.6.0_02-b05, mixed mode, sharing)
TonyM
Hi Russell,
Yes, I am using build 23.
I have been with you since build 13 and have to say that the problem has become more apparent in the last two builds. It did happen occasionally in prior builds but 22 and 23 where I have had to go into the xml. Now sometimes it is the only way I can correct the errors as editing within FSXP just does not 'stick' and correcting one value throws another off and you go into a loop of value fixing.
I'm sure you will fix it because apart from this problem, no, despite this little problem it is a great programme you should be proud of as a company.
Tony
Yes, I am using build 23.
I have been with you since build 13 and have to say that the problem has become more apparent in the last two builds. It did happen occasionally in prior builds but 22 and 23 where I have had to go into the xml. Now sometimes it is the only way I can correct the errors as editing within FSXP just does not 'stick' and correcting one value throws another off and you go into a loop of value fixing.
I'm sure you will fix it because apart from this problem, no, despite this little problem it is a great programme you should be proud of as a company.
Tony