That's it! You would have this in the file after a default install of the 777, (including the section for RAASPRO .dll)

 

 

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">

 

 <Descr>Launch</Descr>
  <Filename>dll.xml</Filename>
  <Disabled>False</Disabled>
 <Launch.ManualLoad>False</Launch.ManualLoad>

 

<Launch.Addon>
  <Name>PMDG Interface</Name>
  <Disabled>False</Disabled>
  <Path>PMDG\DLLs\PMDG_Interface.dll</Path>
  <DllStartName>module_init</DllStartName>
  <DllStopName>module_deinit</DllStopName>
 </Launch.Addon>

 

 <Launch.Addon>
  <Name>RAASPRO</Name>
  <Disabled>False</Disabled>
  <ManualLoad>False</ManualLoad>
  <Path>.\RAASPRO\RAASPRO.dll</Path>
  <DllStartName>module_init</DllStartName>
  <DllStopName>module_deinit</DllStopName>
 </Launch.Addon>

 

</SimBase.Document>

 

ok

 

and where can I find this.dll file

 

 

tks

 

kav

C:\Users\<you>\AppData\Roaming\Microsoft\FSX

 

It's where fsx.cfg and dll.xml can be found, and also exe.xml. We should be maintaining these files and checking them after installing addons.

If other suggestion solutions don't work, you might want to update your bios.

 

I know it is a long shot, but I see your bios cycle is older than the release date of your video card, which means there might have been an update to better support the gtx 600 series.

 

Might be worth trying, as it won't hurt anyways.

Be careful if it's an ASUS mobo, though -- cf. rog.asus.com and read carefully.  There have been later BIOS revisions of some of their boards that have actually been WORSE than the ones shipped with.  They tend to update the BIOS to fix very specific CPU/peripheral/driver version issues, so I would not go that route unless there's an identified problem you have that a new BIOS explicitly fixes.

 

Didn't used to be this way, but has been in the past few years.  Everything's gotten more complex.

I have a freeze after installation Ezdok. Aircraft hangs for several seconds, then everything is fine.

Its either the fault of FS X or your hardware setup..........................Now where is that patch???

I bought the 777 the week it came out and of the 25 flights I have attempted I have had freezes and ctds or fatal errors resulting in fsx quitting on 22 of them.  I have seen more posts on here than I can count from others experiencing the same. I stopped trying to fly the 777 for a few weeks too because it was just becoming tiresome and ruining my whole experience with fsx. I have followed closely suggestions on here as to why this is happening and made every possible adjustment I can think of to fix the problem whilst waiting for the sp1 but still the cts occur and fatal errors.

 

I see posts from those who have never had a single ctd and say the because of that it cant be the 777 in its self causing the problem. they often go on to say that its about compromise in regard to sliders etc and you have to turn stuff down. well I have turned stuff down but the fact is I don't want to turn everything down to a point where the sim looks terrible and half of its features are no longer present , no ai no autogen blocky scenery ,low res textures everywhere etc. I have a fairly powerful pc and why should I have to run fsx in some barebones configuration just to run an addon I have purchased that is meant to run within it. when I bought the pmdg 77 it did not say on the box minimum specs had to be a super computer the min definitions were way below the specs of my own pc and it also didn't say that this addon will not work correctly within fsx as fsx is intended to run but will only work if you run fsx in some terrible bare bone slider configuration.

 

I have even reinstalled fsx and the 777 clean just to see if there was some corruption. Yet still same issues.

 

sometimes event viewer say its 777.dll and sometimes its fsx its self that has caused the crash

on the 3 successfully landed flights I have done I still had numerous freezes. and the only flights I have not had any freezes(with sound) were 2  of the 25 where I turned off every scenery I could other than the area of the world I was flying that route. But even those two flights ended in fatal error some hour in to each

 

sadly I cant see the service pack we are awaiting addressing the heaviness in performance hit if the 777.not wanting to pessimistic but I don't think it will solve this. glad to be proven wrong of course but if I am right and the crashes still occur then I think it will be time to start thinking about asking for a refund.i mean what choice will I have. I cant afford to waste a lot of money on a plane I cant run. its noting personal just pure business sense. none of us are rich are we.

 

I do appreciate the 777 and its complexity and visually how accurate it is and its great textures yes I do but unfortunately if I cant run it because its simply too heavy for an above average pc then its useless to me.

 

I believe that the 777 is not inherently flawed in such a way as its causing the crashes through some coding conflict no its simply to heavy on vas and therefore pushes fsx to its limit .

 

 

the majority of my fatal error flights with the 777 have been hundreds of miles away from any airport addon or default often over the ocean minimal weather or none and not a single ai plane on the radar and pretty high frame rates as a result.

 

so my request is this to all those who say they run the 777 fine with no issues at all please can you post your own fsx setting here so we can see for our selves how you are achieving it. screen shots of your slider screen and graphics configs and any fsx config tweaks you are using would be very helpful.

 

also a note to PMDG. why don't you get in touch with some of us who are having these issues directly rather than trying to replicate what we are telling you on your own machines. why don't you get hold of one of our machines and you can see for your self what is going on. you can cross loop with us / me if you want surely going to the source would be simpler than months of trying to replicate the same issues even if it does cost a bit.

 

 

kav

Kav,

 

If you're willing to do it I'd like to see the results if you clean installed FSX+updates and then literally install nothing other than the 777 and test. (and I seriously mean nothing else - no scenery, no FSUIPC etc) You have to do process of elimination with weird issues like what you're experiencing and this puts the sim in the most base-level state it can be in.

 

Our guide for this is here:
http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx

 

Those VAS numbers at startup are crazy high too - have you followed what's on pages 21-25 of the 777 Intro manual?

For a quick check before reverting to a vanilla FSX, get Scenery Config Editor, put all your addon scenery into a single group, disable this group in SCE by a single mouseclick, restart FSX, do a flight, and report your VAS.

Ryan

 

I am willing to do a clean instal as the very last resort because of the amount of work and time that will involve. its something I have been considering and will do if noting else works because yes I agree its a matter of elimination but obviously its preferable to eliminate items in the easiest way initially.

 

If it comes to it and noting else works I will clean install and publish results here .That wont be happening though until I have at least been able to install the sp1 we are awaiting to see if that helps at all .if not its plan b

 

oh and yes I have followed the intro manual as closely as possible regarding its vas explanation section on those pages

 

 

 

 

and olli4740.

 

 

..I have tried sce but really its just the same as disabling all addon scenery in the fsx scenery tab which I have already tried and disabled all addon scenery plus any areas of the world I am not flying in for that route.

 

 

 

tks

 

kav

kav, I'm not so sure you need go all the way to a fresh install and it likely won't change a thing, unless it's a really bad problem, probably need fresh windows. But have you got FSX going with no addon scenery or any other addons running, and your dll.xml loading only the PMDG items? I would also delete/rename the panelstate files before loading up the 777.

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\PMDG 777X\PanelState

steve

...Fresh update all the Microsoft C++ Redistributables from the MS Download Centre. Look in your Control Panel - Remove Programs list, for the MSVC++ Redistributable items.

hi Steve

 

I am reluctant to start messing around with too much just yet until I have seen the results of the sp1 because why create more work if its not necessary but I will be doing all of this one by one if the problem remains after sp1. as we are expecting sp1 any day now that's why I am holding off. plan b will be after sp1 and I will  then be eliminating absolutely everything one by one until solved . massive amount of work and time but unavoidable maybe

 

 

tks

 

 

kav

Another simple thing that may or may not be a factor at all -- actually two, simple, non-destructive things:

 

1. Go into Control Panel/Uninstall and r-click on Microsoft Simconnect, and carefully choose Repair.  It should go fast and reset some stuff in Simconnect, which can sometimes be a source of issues.

2. Similarly, download the June2010 DirectX SDK directly from Microsoft, and run DXSetup from that; it will reset/reinstall DirectX9 versions, along with related .dlls (x_audio, for instance), making sure you have most compatible versions of that on your system as well.

 

The above might do nothing, but they'll also do no harm, so worth trying.  I've solved a bunch of mysteries that way, especially after installs of things.

 

Also, one other simple thing:

 

Go to fsx.cfg, find the SITUATION= line, and delete everything to the right of SITUATION= .  This will reset your default flight to FSX default, and remove the factors of whatever aircraft you're loading upon FSX startup might introduce as well (if especially cautious, copy what is after SITUATION= into a separate file, to copy back, if there's a specific configuration you want to keep as your startup after this experiment).

 

Again, non-destructive and may also clear up some subtleties.

ok thanks for the suggestions I will try and report back  asap

 

cheers

 

 

kav