Reco01

Cheers guys  thanks 

I have dx 9 the dx12 was just showing in the dxdaig dialog wimdow

Cheers 

Rhys

Happy new year all

My sim pc is 

Asus mother board

i5-4690k 3.5 (4CPUs)

8gig ddr3

Invidia gforce GTX 1650 Tuf 4g ddr6

windows 10 Home

DirectX 12

Not the best PC but for the time being does the job ok I am also running steves DX10 fixer 

I have some tweaks in my cfg file

[JOBSCHEDULER]
AffinityMask=14

HIGHMEMFIX=1

[BUFFERPOOLS]
PoolSize=0

When putting in the tweaks is there an exact location in the cfg file that the tweaks need to go 

Regards 

Rhys 

Hi 

Just delete all those entries and then copy and paste  these three lines into it

[SimConnect]
Protocol=IPv4
Address=127.0.0.1

Save and place the file into your documents folder in file explorer 

Remember too make a copy of the  simconnect.cfg file keeping the original where it is

Rhys

Hi Honus

In fsx se look for the sdk folder and search for the simmconnect.cfg file. Copy it to desk top or somewhere, then open it using notepad delete all the entries and paste these  three lines.

[SimConnect]
Protocol=IPv4
Address=127.0.0.1

save and place the cfg file in to your file explorer documents folder. As mentioned I haven't had a chance to test it out fully.

Regards

Rhys

Hi 

Regarding the API.dll issue I had posted the issue at avsim and got this reply 

Quote

an you try creating a simconnect.cfg file in your Documents folder containing the following 3 lines 

[SimConnect]
Protocol=IPv4
Address=127.0.0.1

Ignore the SDK documentation about this file which is slightly wrong for acceleration and FSX_SE.  Do not add a "Port=" line as it suggests.

That should switch any simconnect users to use IP rather than a named pipe.

Let me know if that reduces or eliminates the problem (or makes absolutely no difference)!

The location in API.dll where your system is crashing is in an callback function that appears to be exclusively used by SimConnect.   I have a theory that the crash occurs if a simconnect user closes the session whilst FSX is trying to send it a message. I know this because I had crashes at the same location and did some investigation on it.   I think that the buffering that TCP/IP uses may make the problem less likely than with named pipes.

Note:  if this does help then ideally we should try and find which simconnect user disconnects during startup and try to switch it to IPv4 rather than switching everyone.  I also don’t know if fsx supports IPv4 for DLLs loaded via dll.xml., it may ignore the setting for these as they part of the same process.

I am stilling doing some testing so won't really know if it has eliminated the issue. I did upgrade my SSD drive from a 256 to a 1TD which was lucky as the original SSD was faulty as I was often getting repair windows blue screen of death. 

Rhys 

Thanks guys

I ran a verify files within steam  but didn't make any difference. Doing some looking on the Internet it seems to be connected to something is trying to access or write to memory, but that's just one theory 

Rhys 

Hi all

Sometimes when I start FSX se, when my flight  loads within a couple of seconds I get the blue  spinning icon and fsx se stops and I am back to the desktop Looking at event view I have located this error message

which is below

 Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: API.DLL, version: 10.0.62615.0, time stamp: 0x559f9ab5
Exception code: 0xc0000005
Fault offset: 0x000e3b9a
Faulting process id: 0x1ddc
Faulting application start time: 0x01da217ff04c1970
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\FSX\API.DLL
Report Id: 151187a8-414b-4c4d-8cd8-c55360c1cec2
Faulting package full name: 
Faulting package-relative application ID: 

Doesn't do it all the time but a little annoying and wondering if anyone here as had the same issue and is there a fix. 

Regards 

Rhys