jackralston

"09 ends only been utilised regardless of wind direction" makes zero sense.

 

This is correct rwy 09L T/O  L -----rwy 27R T/O  L          rwy 09R T/O  L ----- rwy 27L T/O  L

 

So it's a trick you can use to have an AFCAD that regardless of wind direction will only use one end of the runway, Using the xwind technique it makes sure that only 09 end is used. It helps for making very specific taxiway routing AFCADs. Adding xwind runways up to 90deg either side of the real runways makes sure they don't use the other end. 

 

09L - landing only - L yes, T/O no

09R - takeoff only - L no, T/O yes

27L - not used at all - L no, T/O no

27R - have to open to landing to let 09L be used - L yes, T/O no

No luck so far, considering the aircraft generated at stand when I startup FS9 pushback and taxi to 27R with no issues, the technique must work, It is only the ones that land, then taxi to stand and cannot then start the next leg and are stuck in 'clearance' state on stand. It happens on all aircraft types and airlines at various airports.

Thanks, the technique I tried has worked all the time so that it limits 09 ends only been utilised regardless of wind direction as I use the x wind technique on so many airports but only now have I realised it is causing an AI issue (although it never use to). I will go back to my old file which is 27L/09R deps and 27R/09L arrivals. I used the 7.8 technique and it always worked but perhaps it's suddenly causing an issue with AI

Never heard of this before. Why would ai when ready to start their new leg be required to use the same runway they landed on?  If it is for some reason part of the original FS9 code you may be the first person in 13 years to discover this !

I know, absolutely baffling. So basically if you start up at the airport and the plane is already on the ground, the outbound leg will go to the correct departure runway, BUT, if the flight is inbound, lands then sleeps until next leg (1hr later for example) it will for some reason want to go back to the runway used for arrival, so when you look on traffic explorer it can't pushback and is stuck on 'clearance' state for the arrival runway which cannot be used for deps. 

 

This is the first time I've ever had this problem, it's happening at multiple airports too now. 

 

 

Try removing the Take-off/Landing Only restriction for the runways using ADE or AFCAD and see if that makes any difference.

 

Colin B

I'll give that a go and see if it works but i've used this restriction for years on various airports. So for heathrow using 09 ends only it is setup as 09L (takeoff no, landing yes), 27R (takeoff no, landing yes), 09R (takeoff yes, landing no), 27L (takeoff no, landing no)

I've seen similar topics in the past but it appears they are more towards an issue on FSX. I like to do a bit of AI spotting so I setup Heathrow and left it overnight to look at it today (real-time) but I noticed literally every stand was taken, no aircraft were taxiing out. Having looked at the explorer tool, all the relevant departures were stuck in "clearance".

Then having got a bit further with the investigation, I noticed this...

SO!..the setup for heathrow is 09L landing only, 09R departures only. I have used the xwind method to make sure 09 ends are used regardless of weather (which I've done on various AFCADs with no issue). When I start up FS at whatever time, aircraft will be in 'sleep' state then get clearance and then go to 'pushback' state with the runway in traffic explorer showing what they will be going to, which is 09R. 

HOWEVER! 

Aircraft which were spawned enroute to EGLL and landed on 09L will land, go to gate and go to 'sleep' mode ready for the next leg with the runway on traffic explorer still showing 09L (landing runway), therefore when they get clearance for the flight they wont pushback as they can't use 09L for departures and so are stuck on stand! I have no idea why it is doing this all of a sudden. This explains how after an hour or so, the amount of departures dries up!

vector very tempted to do a full reinstall if I cannot find the solution but yes it will take time. I don't think it's a texture issue as it happens everywhere at different airports and different times.

 

HaraldG already deactivated the bgl files in Scenery/Generic/Scenery folder, still no difference. Trying a few more things today and see what happens.

 

Edit: It is only really noticeable at ground level or on approach. When cruising FPS seem to stay stable.

Nothing rogue running in the background. I have tried rebuilding FS9.cfg, getting rid of a few tweaks in terrain.cfg/scenery.cfg, putting back the default autogen default.xml file. It just keeps happening. 

Latest example is starting on 27R at EGLL UK2000 scenery using default C172 and default weather. FPS in cockpit is 45fps, change to outside plane view then switch back to cockpit and it's down to 20fps, once again change to outside view then back and it's up to 45fps....it is truly baffling.
 

Very tempted to reinstall everything but I have so many sceneries/planes/AI/tweaks it would take an age!

This one is a bit baffling as it's only started happening very recently. It happens regardless of which aircraft I use, which airport I am at or whether it is day or night.

 

I keep getting sudden FPS drops whilst cycling through the views. For example, if I am on 2D cockpit view and have a standard 45fps (setting on nvidia inspector) and then switch to VC view of which I usually have setup looking over the wing using active camera, I notice a sudden FPS drop that is very noticeable and causes a lot of stuttering visually. I might have 45fps in one view then it drops down to like 15fps. This also happens on other views too (not just VC view). When in VC view it might be fine, then switch to 2D cockpit and it starts stuttering, CTRL+S to overhead then back to 2D cockpit will then get rid of the FPS drop but it is an annoying cycle.

 

What have I installed/changed?
 

- few changes on my nvidia inspector which I have put to back to my usual settings (no difference)

- FS9Evo (was working fine when I first installed it)

- Ultimate Terrain settings (changed a few settings for Europe/USA/Canada)

 

Can't think what has caused it 

Evening all,

 

Yes I know this is "another one of those topics"..topics! I have been trying to merge the PMDG 737 with the Reality XP WX500 into the 2D panel, unfortunately I keep getting CTD when starting flight using my PMDG/TDS merge. I was previously getting the debug assertion error stuff, ANYWAY, I reckon it is still not working because even though the NDWX.ini file says v.5.2.0, the about section on the RXP menu within FS9 does say v.5.2.1.

 

Does anyone have the correct version/file required v.5.2.0 as old topics regarding this have gone dead.

 

Kind Regards all!  :smile:

Thanks for the replies everyone, rainerk your trick helped adding that to the scenery.cfg, thanks!

Right, I have searched numerous posts/websites/links trying to find a solution to this problem and unfortunately I cannot find anything. Basically the terminal buildings all seem to float a few metres off the ground. Only ground textures/mesh I have installed are UT USA and FSGenesis. Any ideas on how to fix it? 

 

Cheers

FIXED IT

 

If anyone needs help on these pesky issues, I had edited a few effects files for AI lighting and left some comment lines in, I think I just needed to delete them as there were far too many. I also changed a few lines in fs9.cfg that I had commented out too and finally changed a settings in nvidia inspector. So it's either those files or the graphics side it seems!

Yes, another one of these pesky posts! I have looked through the forums enough but cannot figure out what the hell is suddenly causing these. For the past 3 days or so, these keep popping up in various situations.

 

Here's a list of a few things that have been modified/added roughly the time it started first happening:
 

• New LevelD-Skyspirit 767 merge, works perfectly fine considering I did EGCC-KJFK with no issues.
• Used Full Environment 9 (fe9_v1_3.zip) and replaced sky, water, sun. I did not replace clouds. Has worked fine and not CTD'd instantly on startup.
• Tweaked some fx_strobeh lights I had setup for airbus and boeing AI, which have always worked since I started doing them over a year ago.
• Tropicalsim MDPC added, scenery loads fine.
• New AIRAC cycle installed and worked fine for flights at first, recycled back to 1605 cycle and that worked fine too.

I know you can get CTDs from corrupt texture files, I am use to those and usually they make the screen go blank and then says FS9 needs to close. I eventually fix them, but, these new errors are confusing. They have been in various different stages of flight and suddenly pop up and I click 'ok' and FS9 closes.

 

• In flight using Project Airbus A321 merged with Aerosoft panel (always works fine), about 2hrs into flight, cruising, then error appears.
• AI spotting at KATL and EGLL, different times of day, had been working fine for up to 20/30 mins before hand then error appears.
• Spotting at EGLL stuttered for a couple of seconds whilst slewing in top-down view to a new location at the airport then error appears.

Really confused as to what is suddenly causing this. Again, no new aircraft have been installed. I tried to check Event Viewer but it doesn't appear to be showing the errors, as in, it's not creating a new log. There are some past Application errors referring to FS9.exe and they mentioned modules 'MFC70.dll', 'unknown', 'G2D.dll', 'G3D.dll', they are errors from months ago which haven't really appeared since. 

 

I am utterly perplexed :mad:  

would be nice if you shared your solution ... others may have the same issue.

Yes, sorry.

 

Basically make sure FS9.exe is not ticked to run in compatibility mode. I had made the mistake of putting it to Windows 7 and then trying XP, simply unticking it made it work fine  :smile:

would be nice of you to explain your solution ... others may have the problem and need assistance.

 

Yes, sorry.

 

Basically make sure FS9.exe is not ticked to run in compatibility mode. I had made the mistake of putting it to Windows 7 and then trying XP, simply unticking it made it work fine  :smile:

EDIT: Please delete/remove/completely ignore/chuckle at the stupidity of my last post, I've solved it!

EDIT: Admin please delete, I've solved it! 

Hello all.

 

Since moving over to Windows 10, everything worked fine, although I have no found an issue.

 

The weather radar map for the Wilco Airbus Evolution package no longer works. I click the weather radar "on" but no test sweep appears and no weather ever appears on the display. The rxpWxSim.dll is still in the "Feelthere > Airbus" directory, I tried putting it in the FS9 Modules folder but on startup FS9 said the file was not compatible and wouldn't be used. It worked absolutely fine in Win 7, but I can't seem to get it to work. 

 

Any ideas?

I have found one issue which I haven't been able to solve yet. 

The weather radar map for the Wilco Airbus Evolution package no longer works. I click the weather radar "on" but no test sweep appears and no weather ever appears on the display. The rxpWxSim.dll is still in the "Feelthere > Airbus" directory, I tried putting it in the FS9 Modules folder but on startup FS9 said the file was not compatible and wouldn't be used. It worked absolutely fine in Win 7, but I can't seem to get it to work. 

 

Any ideas?  :smile:

So I recently decided to use 'Nick's LightFix' and I love it and I even managed to fiddle around with the strobe.fx files to create a double-blink airbus strobe. But I've got one picky situation I'm now trying to sort out with the navigation lights.

 

So for the medium aircraft sizes I use fx_navredm.fx and fx_navgrem.fx, the heavys I use fx_navredh.fx and fx_navgreh.fx and I've noticed I can only see the red/green colour when close up to the aircraft. If I am close up, I can see red/green, once I move back a bit (not talking a long distance) it ends up going to a standard white colour. It seems as if the texture file is only noticeable when at a certain distance.

 

So my question is this. Is it possible to change the distance the texture file becomes 'seeable' in the fx file. Once again, when close up, I can see the red/green fine. Once backing up and spotting for say the tower, it just appears as a white light. The beacon and strobe lights are fine though, the beacon will still appear red at quite some distance.

 

I have attached two files to demonstrate what I mean.

 

First one, at a bit of a distance notice how it's just the white light, it isn't shown the green/red texture.

 

Second one, closer to an aircraft, the closer one shows the red nav light, but the second further aircraft still shows white light instead.

 

 

(Also posted at fsonline.dk) 

 

Right, first post and I know what you are thinking, another newbie who clearly hasn't gone through the forum. 

Unfortunately, I would just like a bit of help getting to grips with the markers and making my own IFR clearance file. I have already made files to say "FL170" (from FL070 all the way to FL190) instead of "17000" so hopefully this comes across ok. 

I would like to create a new IFR clearance request like this... 

<agent>, <callsign>, <ac_type>, information <atis>, stand <parking_gate_letter><parking_gate_number>, ready to copy clearance to <airport_destination_request> 

 

So it would read as...

 

"Manchester Clearance Delivery, Virgin 3046, Airbus A320, information Alpha, stand 18, ready to copy clearance to London-Heathrow"

Now, I thought it worked by adding the "information", "stand", "ready to copy clearance to" sound clips in. I tried this, and the text on the screen in ATC window showed it as I expected, however the verbal dialog only said "information, ready to copy clearance to ......." 

So, I tried markers (albeit not very successfully I imagine) and now the text on the ATC window doesn't show up and neither do I hear it and instead the first I hear is the readback. 

If possible could someone just tell me EXACTLY how to make this one work? Sorry to be a pain, thank you much kindly

VATSIM-UK presents Manchester Fast4ward2/2Following on from our last Fast4ward event, we are now condensing an entire days flight schedule at Manchester Airport (EGCC) into 8 hours, between 1400Z and 2200Z on Saturday 6th February 2010.Outside the London group of aerodromes, Manchester Airport is the busiest in the United Kingdom handling in excess of 22 million passengers per year. Manchester (EGCC) will be fully staffed for the duration of the event from Delivery through to the overlaying TMA.Charts are available and pilots are reminded to familiarise themselves with them before the event. Pilots are welcome to attend without booking, however be aware that priority will go to scheduled flights ;)Charts are available here!Book your flight here!Pilot's Briefing DocumentWe look forward to seeing you on the day where our team will guide you safely and expediently to and from the aerodrome.

VATSIM-UK presents Manchester Fast4ward2/2Following on from our last Fast4ward event, we are now condensing an entire days flight schedule at Manchester Airport (EGCC) into 8 hours, between 1400Z and 2200Z on Saturday 6th February 2010.Outside the London group of aerodromes, Manchester Airport is the busiest in the United Kingdom handling in excess of 22 million passengers per year. Manchester (EGCC) will be fully staffed for the duration of the event from Delivery through to the overlaying TMA.Charts are available and pilots are reminded to familiarise themselves with them before the event. Pilots are welcome to attend without booking, however be aware that priority will go to scheduled flights ;)Charts are available here!Book your flight here!Pilot's Briefing DocumentWe look forward to seeing you on the day where our team will guide you safely and expediently to and from the aerodrome.