|
Post by hermankreimes on Oct 9, 2009 10:30:50 GMT -5
Hello MikeW;
Thank you for your reply and input. I am experiencing exactly what you mentioned. I checked the TMVL in FS9 cfg and it is set at 19.
I think what I have trouble with understanding is the fact that on my initial installation of 1963 Paris Orly is, that everything came up as it should. The underpass and roadway was there and diplayed properly, and this was in no way effected by the revision I made to the RW26\08 length.
Unfortunately I needed to make a few further changes and I thought it best to just delete everything and start over again. ( I had also cleared out the recycle bin ) I re-installed the same files that I had used before and the scenery problem started.
I downloaded the files again from flightsim and did another install without making any changes to the AFCAD, but still no success. The mystery remains.
Herman
|
|
|
Post by Harry on Oct 9, 2009 10:39:39 GMT -5
Hi all, As Wolfgang said the Orly scenery was very complicated to do. Because the tunnel is below "normal level" I had to work at two levels. That's the reason the scenery sometimes will not work properly........, I know Maybe the best thing you can do is to close FS9 and start it again. With me it works Kindly regards Harry
|
|
|
Post by hermankreimes on Oct 9, 2009 10:50:47 GMT -5
Hello Wolfgang;
Thank you for your reply. Yes, one thing is certain, had I not attempted to make any changes to the Orly airport all might be OK, but I have the feeling that most serious flight simmers are striving for as much reality as is possible.
True, the runway lengths as shown are certainly sufficient for even the largest of piston engined aircraft, however, not for the intercontinental jetliners operating from Orly in 1963.
I fully realize and understand, that when this airport scenery was designed, there was insufficient data available, but since then some reliable information has surfaced and that was the reason for me to make an attempt to update the airfield.
After quite a bit experimenting I found the whole thing interesting and it proved to be a good learning experience.
Herman
|
|
|
Post by Defender on Oct 9, 2009 13:28:06 GMT -5
Herman, Use this link for LFPO s493.photobucket.com/albums/rr294/bill749/?action=view¤t=LFPO1965.jpgIgnore 07/25 which was a mid 60's addition. The white lines across the runways may be displaced landing thresholds - I don't know. For those who use Flight Global's archive, this comes from the 1 December 1966 edition. However for some odd reason much of 1966 seems to be missing from the archive. I just happen to have kept the original magazine. Bill
|
|
|
Post by hermankreimes on Oct 9, 2009 14:44:59 GMT -5
Thank you once again Bill for your assistance. I do believe that the white line indicates a displaced threshold judging by where the taxi way joins the runway 26. I believe that whenever the actual extention to the runway was made this is also what it looked like in 1963. Thank's again.
Herman
|
|
|
Post by emfrat on Oct 11, 2009 4:33:10 GMT -5
Hello Herman - I have been away in NSW visiting my grandkids, so I wasn't able to reply earlier. When I set up my dual install, I had Microsoft Games\FS9_Classic and Microsoft Games\FS9_VFR. I originally had one file called FS9_VFR.cfg and another called FS9_Classic.cfg and each one lived in its main folder, not in Docs&Settings\Application Data\Microsoft\FS9 where a default install puts FS9.cfg. I had been led to believe that this was correct and the ones now found in their main folders would be used, rather than the default one in AppData,.
I then found that my WoAI installer was not finding the modern (VFR) installation because it looks for FS9.CFG and that was not there. So I renamed FS9_VFR back to FS9.cfg, and that was fixed. However I then found that FS9_Classic.exe was using the FS9.CFG instead of my FS9_Classic.cfg So I put both cfg files back into AppData and made the 'Target' field in the properties of the FS9_Classic shortcut icon look like this: "C:\Program Files\Microsoft Games\FS9.1_Classic\FS9.exe" /CFG:"%APPDATA%\Microsoft\FS9\fs9.1_classic.cfg" NB there is a space before /CFG and that forced it to use the correct cfg. I don't know if you have a dual or single install, but I suspect that your TMVL=19 is not being picked up, for the reasons outlined above. That's all I can think of - hope I haven't confused things further. ATB MikeW
|
|
|
Post by hermankreimes on Oct 11, 2009 13:34:03 GMT -5
Hello Mike;
Thank you for your response and input.
Since I only have a single install for FS9, I probably should not have the problem that you experienced, but thank you for taking the time to provide your suggestion.
Herman
|
|