roshanf

Me as well. Can't wait for Rex Texture Direct (with soft clouds) to be updated, however, in their recent update statement REX makes no mention of v5 compatibility for Texture Direct :( I am not too sure if I messed up something in v5 but my grass textures are all blurry. Was hoping to use Texture Direct to improve grass textures but I guess we'll have to wait for it. Any one else have really crappy grass in v5?

Thanks KillaBee, tried everything listed in this thread but nothing seems to help. I moved ORBX!Vector right below Africa and above 1107 Base and renamed CVX6725.bgl from the ORBX Vector folder. That way only Mumbai is affected by this change and nothing else as far as ORBX Vector is concerned. I'd rather fly with a working airport than with working land class if given to choose. VABB works perfect, only the land class info is dated.

For those using ORBX Vector try moving ORBX!Vector below 803 in the scenery library. Messes with some of the new road data associated with Vector like the sea link but it fixed all my runway issues including the sinking issue and the dual taxiway marks.

@ Hasegawa I have a similar issue with losing the engine blades. Have you found a solution yet?

PMDG_777x.dll seems to be faulting for me as well. Here is the error I get. Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: PMDG_777X.DLL, version: 1.0.0.0, time stamp: 0x52256029 Exception code: 0xc0000417 Fault offset: 0x0022035a Faulting process id: 0xd10 Faulting application start time: 0x01cea96b49574811 Faulting application path: D:\Program Files (x86)\Microsoft Flight Simulator X\fsx.exe Faulting module path: D:\Program Files (x86)\Microsoft Flight Simulator X\GAUGES\PMDG_777X.DLL Report Id: f8aba82f-155f-11e3-bf16-00241d721728 Faulting package full name: Faulting package-relative application ID: It seems to work fine if I load only, and only, the 777. The trouble starts the moment I try to switch between aircrafts or ending a flight with the 777. The only solution for me as of now is to restart FSX every time I finish a flight or would like to change to another aircraft /reset the flight. I have written to PMDG support for the issues reported above and here is what their kind technical support had to say. Quote: "The aircraft cannot be loaded over itself, period. There are long-standing bugs in FSX that prevent us from re-initializing some critical internal variables when the gauge loads over itself like that. Every airplane we've ever made for FSX has this limitation, as do many other complex addons that have FMCs and finite-state systems modelling like this. Something weird or an outright crash happens to all of them." A dead giveaway for the problem is when you look at the 777 moving animation on the Free Flight page after ending a 777 flight. I have attached a before and after image of the 777 and on the 2nd one you can clearly see that the engines have lost their blades. Kinda looks like those impulse engines on star trek. I can suggest trying to plan ahead and use only the 777 before restarting FSX. See if that works for you'll. Edit Forgot to mention that I tried formatting and reinstalling Windows and FSX. That really does not help. For those who have a problem loading a 777 dll file at FSX start up or starting a flight with the 777, try creating a backup of your fsx.cfg and dll.xml and deleting them from its default location. If it works you know where the problem is and will have to figure out which lines in the original files are creating a problem. If it doesn't you can safely restore them from the back up.