chumley

I've bought my last offering from Imaginesim. I emailed them at the end of April and received a response from Cal saying he would look into my issues - both the runway lights and the misaligned AFCAD but nothing has eventuate. Sceneries are overpriced anyways.

I've been in contact with Ryan and he is stumped by these problems. I have followed the instructions in the file you mentioned but without success. The dll.xml has a single entry in it when the NGX is loaded and that is the HUD interface dll. When i load the 777 a couple more are added - RAASPRO and the PMDG Interface. I'm planning to uninstall the lot including the OS and start again but have the PC think it is a standalone not part of a LAN. I want to trigger the activation which doesn't happen at the moment and see if that makes a difference. I have loaded the Aerosoft A320 and I get asked to enter serial details during the process. Can't understand why PMDG doesn't but that may be down to my my level of understanding of these things. I only want to have the NGX and 777 loaded on two platforms for a short space of time while I move everything across to the newer higher specced machine the FSX (Boxed) will be removed and with it the PMDG products. We'll see what happens over the coming days.

When the NGX is first loaded in FSX SE and is also loaded in FSX MS (on a networked machine) does it apply the normal activation routine? I have both the NGX and T7 loaded in FSX SE and basically neither will load and crash FSX when selected. Ryan is looking at the problem but I wondered if anyone else has a similar setup and is managing to get the thing to work. Thanks

It won't worry me as I don't have 'Ultimate Terrain' installed. The files were packaged with the freeware scenery. Can't remember which it is but when I do i'll take a look and if it is not functioning OK, rip it out. Thanks for your insight.

I have the scenery mentioned and it doesn't exhibit the strange behaviour described. However, a short while ago I had all manner of issues with a scenery at Bali where I couldn't get rid of some default scenery impinging upon the addon. I thought I must have another Afcad loose some where so painstakingly went through the scenery config disabling different sceneries to identify when the problem disappeared. After some detective work I found the issue related to another scenery I had which had a whole lot of bgl's - some starting FL*****, some HL*****, some HP*****, some RD*****, RR*****, some ST***** and some UT***** where ***** is a 5 digit number. After removing them everything worked OK. No idea why the folder of unusual bgl's is present as the scenery appears to work OK without them and I have no idea where they come from or the reason for them. May help.

Checked out the new AiMonitor and it worked for 6 of the 7 identified folders. Closer examination showed the scenery folder it didn't work on was one which was empty other than an advisory text file. I moved a .bgl into it and it worked flawlessly. However, in an attempt to take this folder out of the equation I deactivated it and ran AiMonitor. The message was displayed as though it were active. Is the scan and decompile action supposed to ignore deactivated lines in the scenery.cfg? I guess the solution to this is to have the scan process ignore folders without a .bgl file present but I would suggest it should also ignore deactivated scenery files. Anyway, thanks for the prompt attention to this matter.

Hi Roland Hotfix 7 has brought some issues to my installation. I have tested this on both my network machine and on the main FSX machine. Once the new executables are installed and I run the 'Force Update of Runway and Taxi Data' I get a number of messages (7) displayed that indicates a scenery path cannot be found. As nothing has changed other than the new executables I reverted to the older versions and ran the 'Force Update of Runway and Taxi Data' and it sailed through without a single error message. The Tax_graph.txt file also increases from 2834 to 2875 with the changed .EXE files if that means anything. Below is an excerpt from the Scenery.cfg file for one of the paths. It resides in E:\FSX: [Area.216] Title=FTXAU15_SCENERY Local=ORBX\FTX_AU\FTXAU15_SCENERY Layer=213 Active=TRUE Required=FALSE

Not suggesting they should - just wondering why they haven't if the answer is available programatically.

Yeah - installed each of them. Not sure where to go from here - probably PMDG ticket time.

You have heard the term 'your mileage may vary' - well my mileage is currently zero success. I have it installed and right now the only think that works is the base system. I have downloaded the corrected versions of the PMDG NGX and 777 and the Aerosoft A320. Neither will work and right now I'm think that I would have had more fun using the $25 as paper starter for a BBQ. I will keep persevering but there is a somewhat nasty taste in my mouth that won't easily go away. Having said this there are others for which this has been a godsend.

OK - there must be something more going on then. I'll persevere and see what comes of it but I must say I'm not that confident of success. Seems strange it loads into FSX SE without a problem, each of the four Simconnect modules are identified in 'Currently Installed' programs, the aircraft is able to be selected from within FSX SE and yet when it is selected it effectively fails to load correctly to the point where I can select either a time of day, airport or finalise the load and bring it into use.

Understand Kevin - begs the question though if a fix is available why hasn't PMDG or some other developer built it into their offerings as an inducement to buy?

I'm somewhat skeptical about this after reading what Robert Randazzo has to say earlier in the thread. If, as suggested, the fix can only be made in the guts of FSX I would suggest that Dovetail or LM will probably be the ones to resolve the problem in a distributable way. Having said this I am more than happy to take a giant piece of humble pie and eat it with good grace if I am wrong. The ball is now in Holger's court to dispel my skepticism.

I have the Steam version of FSX loaded on a network machine and the original NGX still loaded on the main machine. They will eventually change places in the hierarchy when the time is right. Am I able to load the NGX on the Steam machine without removing it from the original installation or must this be done first? I was hoping I would be able to continue with FSX MS while migrating all my stuff to FSX SE but if that isn't possible then I'll have to do what with the migration then make the break. I did (have) followed the instructions in the file you mentioned.

I have just downloaded and installed FSX SE. I downloaded the latest version of the NGX, 777 and the 777 expansion and loaded them into FSX. It struck me as unusual that I wasn't asked for a Serial Key but continued. When I opened FSX the aircraft were in the directory so I selected the NGX and the process froze on me. Now it is cycling between responding and not responding as seen through Task Manager window with the image of the aircraft being replaced by a black window. When the image returns it has rotated a few degrees but at that point is not responding. Any suggestions?

Interesting. I think ALL the FS world would be interested. How may I ask did you do it?

So, let's say if they can't add to FSX but can fix errors. If that is the case are they able to and going to fix the error that causes the VC panel eyepoint to move incorrectly as it does in larger airliners?

It is easy to do just this. I had AiController happily whirring away then accidentally clicked over the button and all went pear shaped the next time I loaded. I thought I would be in for an evening of adjusting and testing then noticed the change. Perhaps a big message identifying the Sim for which it is being prepared could be incorporated at the start requiring a response before initiating the load routine. Just a thought.

Probably what is happening is that when FSX first starts to run the wind is in one direction and AI are assigned runways to match. They will continue on this assigned approach until all that have been assigned have landed. However, if the wind direction changes sufficiently in direction by say a weather program kicking in, new AI are assigned from the opposite end. There is a setting under the Options tab to force a certain runway into use. this will make aircraft incorrectly assigned break away from their approach and set up for the forced runway.

In my case the airport is an add-on - ypph_rs_fsx.zip

The developers have in recent weeks released the P3D version and an update version for FSX for WSSS. When the update is installed there are no runway lights visible. These lights are displayed in the previous version. is anyone else experiencing this problem?

In relation to the first issue - the AI was already there at Gate 55 from the start of my FSX session and the arriving AI were both directed to Gate 55 after landing. In the second issue - it didn't use the vacant Gates when it should have.

Sorry Roland, I wasn't as clear as I might have been. My apologies if you have been searching the 'haystack' for a non-existent needle. I am running 1.4.1.5. Gate 55 was occupied. The UAE flight was assigned to Gate 55 and taxied to it stopping over the top of the 'sleeping' AI. One of the AI disappeared (not sure which as I was taxiing to the active and observing airport activity on EFB. While I was still taxiing the SIA AI arrived and was assigned Gate 55 by AiController. I didn't see the outcome as I had taken off. What I am interested in is if all gates identified for SIA are taken should AiController direct any SIA AI to a vacant but compatible gate? This has given me the idea it would be nice to see the gate number shown against the 'sleeping' AI if possible and also in the column for aircraft type i.e. Jet, Turbo etc. could you display the aircraft type as A330, B737 etc.?

Further to the above post, just left YPPH and while taxiing two flights arrived both Triple7's - one SIA and the other UAE - and both were directed to an already occupied Gate 55 (the gate is identified for both airlines). These instructions were given even though Gates 52 and 53 were unoccupied both being identical in size to Gate 55 and neither having any specific airlines identified. Should AiController have chosen one of the vacant gates?

Just loaded HotFix 6 and the 'doggie style' parking is back. I was at YPPH and gate 13 had an AI on stand and it had been there for quite a while as prepared for departure from gate 14. An arriving 767 was given taxi instructions to gate 13 and when it arrived it remained for a few seconds then disappeared. is this the way it is meant top work?