Hi folks

So when I arrive (when I depart its fine) as FSDTs KDFW, things mess up. No terminal markings, no follow me vehicle.

I contacted FSDT, and got this in reply:

 

That's just confirms what I've said: you are seeing parts of objects, which means everything on our side is running correctly ( if it wasn't, you wouldn't see anything ), so it's surely a video driver/settings problem.


Try all the following:

- Update your video driver

- Reset your video driver settings to default

- Reset the FSX settings to default, by removing the following file:

%APPDATA%\Microsof\FSX\FSX.CFG

This will force FSX to rebuild a new config with all default settings. After doing this, be sure you apply the HIGHMEMFIX tweak in the Addon Manager, save the settings and restart FSX.

     

Now, i'm not doubting this FOR A SECOND. I believe it. I just want to see if you guys have got a way round fiddling around it all, or if there's something else I could do? I just want a bit more say with it! That's all! I DO trust this guy!

Here's a picture for you all to see, too!

Thanks! http://www.flickr.com/photos/16145332@N07/10678717443/





 

 

 

So when I arrive (when I depart its fine) as FSDTs KDFW, things mess up. No terminal markings, no follow me vehicle.

 

This may sound like a stupid question, but you didn't specify in your post:

Have you checked recently to ensure that you're not seeing the same thing with other aircraft?

 

Since it shows up on departure, but not on arrival, my thought is that it's a driver or memory issue.  Do you have the HIGHMEMFIX in the cfg currently?

This may sound like a stupid question, but you didn't specify in your post:

Have you checked recently to ensure that you're not seeing the same thing with other aircraft?

 

Since it shows up on departure, but not on arrival, my thought is that it's a driver or memory issue.  Do you have the HIGHMEMFIX in the cfg currently?

As of before the 777, the NGX seemed to work fine!

I HAVE NO IDEA :lol:  How do I check? And if so/not, what do I do and what will it do? :mellow: 

 

 

 

I HAVE NO IDEA   How do I check?

 

...you check by switching to another plane and trying a flight to DFW to see if it messes up the same way.

 

 

 

And if so/not, what do I do and what will it do?  

 

If it still looks messed up, it's not a problem with the 777 and the change is only coincidental.

If it doesn't look messed up, then it may be something that changed after the 777 was installed.

 

Troubleshooting 101:

http://www.techrepublic.com/blog/user-support/how-to-troubleshoot-a-computer-problem/

 

 

...since it's your ground vehicles and so on, I'm guessing it's GSX-related.  Have you tried restarting Couatl?  You do this by using the Add Ons menu, and in there you should find some reference to GSX or Couatl ("Couatl Powered Products" or something like that).

 

Do you, perhaps, need to register your FSDT scenery?  I know FlightBeam's IAD will kill all the buildings and so on after the trial period ends.  Perhaps your FSDT scenery does similar, which would explain why it's fine for departure, but not arrival.  Registering fixes this issue.

...you check by switching to another plane and trying a flight to DFW to see if it messes up the same way.

 

 

 

 

If it still looks messed up, it's not a problem with the 777 and the change is only coincidental.

If it doesn't look messed up, then it may be something that changed after the 777 was installed.

 

Troubleshooting 101:

http://www.techrepublic.com/blog/user-support/how-to-troubleshoot-a-computer-problem/

 

 

...since it's your ground vehicles and so on, I'm guessing it's GSX-related.  Have you tried restarting Couatl?  You do this by using the Add Ons menu, and in there you should find some reference to GSX or Couatl ("Couatl Powered Products" or something like that).

 

Do you, perhaps, need to register your FSDT scenery?  I know FlightBeam's IAD will kill all the buildings and so on after the trial period ends.  Perhaps your FSDT scenery does similar, which would explain why it's fine for departure, but not arrival.  Registering fixes this issue.

Hang on, so, To sum up:

Check NGX

If all ok, should I do something with that "HIGHMEMFIX" ?

Or just go straight to Reinstall GSX?

 

Sorry for being a bit of a "noob" here, (or worse), its been a lawng time since I've asked questions on here, and, in fact FS....

 

 

It might be a wild goose chase but check that it hasn't been un registered as mine was and it turned out fine when leaving as wasn't there long enough for it to be affected but when arriving it preloads etc and by time landed it had disappeared

 

 

If all ok, should I do something with that "HIGHMEMFIX" ?

 

Go into the FSX overhead menu and click Add-ons.  Go down to "Add-on Manager",  A screen titled "Vir-tuali" will show up.  Under product go to "Dallas-Fort Worth".  On the right will be a screen of "FSX Tweaks", find "HIGHMEMFIX", if it says "1" then you have the HIGHMEMFIX installed. 

 

Billy Bluestar 

 

 

Check NGX

 

Check the Default Cessna for all it matters, really.  Just not the 777 to rule it out.  The thread title makes it out that you're assuming the issue is caused by the 777.

 

 

 

If all ok, should I do something with that "HIGHMEMFIX" ?

 

This should be in your FSX.cfg regardless of this troubleshooting.  If it's not in there, add it in.  If you don't know what to do, google it - there are more than enough tutorials, articles, and threads about it and why you need it.

 

 

 

Or just go straight to Reinstall GSX?

 

NEVER. EVER. Reinstall something until you've exhausted all other options.  People suggest it way too much, and it can cause more issues than you're trying to solve.

 

You'll note that I have not suggested it yet because there's no reason yet.

 

If you're referring to my earlier comment about reSTARTing Coatl, that may fix it.

Not having highmemfix is the problem here. If the person doesn't know what it is, then they certainly have not ever added it to the fsx.cfg file

Not having highmemfix is the problem here. If the person doesn't know what it is, then they certainly have not ever added it to the fsx.cfg file

Nope, never tweaked FS ever. So I should add this anyways?

Check the Default Cessna for all it matters, really.  Just not the 777 to rule it out.  The thread title makes it out that you're assuming the issue is caused by the 777.

 

 

 

 

This should be in your FSX.cfg regardless of this troubleshooting.  If it's not in there, add it in.  If you don't know what to do, google it - there are more than enough tutorials, articles, and threads about it and why you need it.

 

 

 

 

NEVER. EVER. Reinstall something until you've exhausted all other options.  People suggest it way too much, and it can cause more issues than you're trying to solve.

 

You'll note that I have not suggested it yet because there's no reason yet.

 

If you're referring to my earlier comment about reSTARTing Coatl, that may fix it.

Will do

Ok

AND I NEED TO LEARN TO READ! (I mess up in exams by misreading too! :( )

 

 

I will be testing tomorrow evening so I will update on here!

 

 

 

 

So I should add this anyways?

 

I already told you: yes.

 

Not sure how else you can interpret what I wrote earlier, so I'm going to highlight and stress certain points, just to be sure it sinks in:

This should be in your FSX.cfg regardless of this troubleshooting.  If it's not in there, add it in.  If you don't know what to do, google it - there are more than enough tutorials, articles, and threads about it and why you need it.

 

 

 

 

Will do
Ok
AND I NEED TO LEARN TO READ! (I mess up in exams by misreading too! )

 

Yep.  You do.  Take time.  Slow down.  Read.

 

Nobody is timing you.  :wink:

 

 

Nobody is timing you.  :wink:

HOW CAN YOU BE SURE!? hehe

Flew the Baron from Love to DFW, like I did with the 777 test flight, turns out with the B58 it worked perfect, jetways, exterior bits and safedock systems. The follow me truck even appeared (if you look at my orig picture, only the lil guy and the flashing lights show up), so later on i'll modify the CFG (IF I HAVE TIME- time has been short for me eh!)  and update here!

 

 

Love that new Banner Kyle! :biggrin:

 

 

 

 

 

 

 

Love that new Banner Kyle!

 

haha - thanks.  I got tired of the few people using it like it upsets me, so I just turned it into a badge of honor.  My way of driving the point home that you can call me whatever you want.

DFW dreamteam and my 777 work fine together, but FPS takes a hit when at DFW.....

DFW dreamteam and my 777 work fine together, but FPS takes a hit when at DFW.....

Ahh, but I suspect you have HIGHMEMFIX added?