Hi all,

 

I am using an i5 3570K overclocked system (4.5Ghz) and Prepar3D. My Graphics card is the Asus nvidia GTX660

 

I have a tweaked .cfg file according to the tuning guide of P3D.

 

My problem is that in 50% of the flights I do, after approximately 2 hours of flight a shuttering is starting with a 1Hz frequency (every 1 second the frames stop and go).

 

This is really frustrating as you can imagine as it ruins the flight. Actually if I leave the problem and continue the flight it became worse (more milliseconds pausing when frames stop) and eventualy the sim will crash giving me a CTD.

 

I tried deleting the .cfg and letting the sim to recreate it, then added the tweaks again, but the same just happened..

 

I would be really pleased for any suggestion for how to deal with this problem.

 

I am looking forward for your help!
 

Regards,

Ifikratis

Which aircraft?

Are all optional sliders at minimum .. and no AI traffic?

No Wx program running?

Thank you for your reply.

 

Ι fly the Aerosoft Airbus X Extended A320/321

 

Slides are not all to minimum.

 

 

My Scenery settings in Prepar3D are:

 

Level of detail radius: Very large 5.5

Mesh complexity : 90

Mesh resolution: 10m

Texture resolution: 1m

Land detail textures : Checked

Water and Bathymetery

Reflection detail: Sky, Clouds, Sim Objects, Terrain

Bathymetry : Not elabled

Scenery complexity: Very dense

Autogen complexity : None

Ground scenery shadows: not enabled

Special Effects: High

 

 

AI Traffic : minimum

 

 

For weather program I use OPUSfsx with REX graphics (no rex weather engine)

Removed the BP tweak and the problem reappears...any suggestion what it might be causing it?  :(

^{Try using the default cfg file. Rename the old one and let P3D rebuild. See if you get stutters. Start adding back tweaks until you do.}

 

^Vic

Do you use the CPU affinity mask in the cfg ?

I used to have stutters because FSX was running on the first CORE (used by windows and some other softwares) : try using the AffinityMask (in JOBSCHEDULER) option to have fsx NOT running on the first CORE (or on the 2 first CORE/threads to leave free cpu to other programs).

 

 

Guillaume

I use the following tweaks:

 

 

[bufferPools]

Poolsize=0

[JOBSCHEDULER]

AffinityMask=14 

 

[Main]

FIBER_FRAME_TIME_FRACTION=0.12

 

[GRAPHICS]

HIGHMEMFIX=1

ForceFullScreenVSync=1

 

 

I tried several settings...including removing  the BufferPools tweak, then I removed only the HIGHMEMFIX=1 tweak, but shutters occur again.

 

If I use the above settings as long as the nvidiainspector settings proposed by the 'Word Not Allowed blog' I get a very smooth performance.

 

The problem is, that when I do a flight witch is longer that ~2-2.5 hours a problem appears that drop the frame rate from 30 to 14-15 . A behavior that repeats every 1 second...Visually it appears like the sim starts and stops every new second.

When the problem appears, it does not stop. P3D consumption in the Task Manager is ~85% witch is normal I think.

Also the sim willl eventually crash if I continue the flight for many more minutes or if I select to enter a menu.

 

I am back from a format and formating again is not an option for me...It took more than 3 days to install all add-ons, aicraft and software I use...

 

Any other suggestion would be appreciated..

 

Best regards,

Ifikratis

Are you getting an OOM error message with the crashes?

 

What happens if you use a default aircraft (jet or prop).

All optional sliders at minimum.

No AI traffic.

No Wx program running.

Just as a FYI, the HIGHMEMFIX tweak is not needed with P3d as it is corrected in the code.

 

Sounds like you may have a memory problem of some kind. It would appear that memory is being used up over the long flight and as it gets to max, you get the stutters.

 

I'd start by shutting down any running programs or processes in the background that are not absolutely necessary.

 

IMHO, playing with tweaks is not going to solve this issue.

 

Vic

Guys thank you very very much for your replies.

vonmar, I get a message saying that P3D is closing , I don't get any code or error report. I have not tried doing the same flight with all sliders to minimum as I try to find the way to eliminate the problem without loosing the simulator appearance. However it may be an option to do what you say. I think that if I move all sliders to minimum and if that eliminates the problem, it is not a solution for me. The whole testing is also very time consuming as I have to do a flight for more than 2 hours to test.
(and I just ruined a flight in IVAO from Athens to Barcelona, 20 minutes from touchdown because of that.. :Cry: ).
By the way I have lost nearly a week trying to figure this out with no result.

vgbaron, I have also read that but the HIGHMEMFIX tweak is proposed by the Prepar3D Learning Center, so I don't know what to believe...people or the P3D developers tuning guide..When I removed it I got an crash 10-15 after starting a flight (still in the gate), so I reenabled it. I don't know however if this was because I removed the tweak or another source. I haven't got random crashes since though (with highmemfix enabled).
I agree with you, ti also seems like a memory problem. If I was using a HDD I would suspect someproblem with this, but I use an SSD drive and no HDD installed at all in my system. Also, RAM consumption seen in the task manager, when the problem appears seems normal (around 50-60%).
By the way, my system specs are the following:


Motherboard: Gigabyte Z77X-D3H
CPU: i5 3570K
GPU: Asus nvidia GTX-660
SSD: Samsung 250GB
RAM : 2 x Corsair 4GB 1600MB
PSU : Corsair VS650
Cooling: Corsair H100i hydrocooler
Case: Corsair Carbide

The system is overclocked to 4.5Ghz changing the baseclock, turbo:off, and VCC=1.320
I have tried lower settings like 4.4Ghz, VCC=1.285 but the same problem happens.

I also, tried several times to spot some program or process that seems suspicious but I couldn't find any uknown or not systemic process. Of course I don't know most of the processes, or what they do...(windows processes etc..)

So, vgbaron I agree playing with tweaks may will not solve the problem...So, are there any more specific suggestions?
Thank you very much again for your time

What happens if you use a default aircraft (jet or prop)?

All optional sliders at minimum.

No AI traffic.

No Wx program running.

 

Then if no error ... you add one back at a time until the problem surfaces ... then you know!

 

Did you build your own PC?

Is it on a home network?

 

All errors are logged in the Windows Event viewer ... tell which module caused the problem.

Did you try FSUIPC OMM to watch your memory usage during a flight?

One more .. for testing.

Shut off the overclocking.

 

"I just ruined a flight in IVAO from Athens to Barcelona, 20 minutes from touchdown because of that."

Do it happen on non-online flights?

Was payware destination scenery being used?

Was destination Wx being loaded?

 

Are you using FSInn?

Thank you!

 

So, vonmar you suggest to turn of overclocking first..then turn all sliders to minimum, then use a default jet and do the same flight again. No AI traffic is already set and also no test without weather software running. Ok! i will do and report.But before that, please check the replies to your questions. It would be better to avoid this time consuming method.

 

Yes the PC is build by me, but I am not an amateur in this, and everything was working correctly some months ago. Then for other reasons I did 4-5 formats the last 3 months, and trying to establish a smooth P3D installation since...

 

''Do it happen on non-online flights?

Was payware destination scenery being used?

Was destination Wx being loaded?''

 

I tested on a non-online flight yesterday and the problem didn't happened.

However I am a bit unlucky to this, because yesteray I also did a flight online from London to Athens (3,5 hours) and also the problem didn't happened.

But 90% of the time, it will happen.

Destination scenery is irrelevant as the problem happens way before I reach the airport area, when still in cruise.

 

''Are you using FSInn?''

 

No, I am not using FSInn.

 

''Did you try FSUIPC OMM to watch your memory usage during a flight?''

 

No, I am not aware of this, could you tell me how I can see that?

 

However the best solution is i think to look to the event viewer as you proposed. I will try that now and tell you what I can find.

 

Thank you very very much again..

I found these reports :

 

1)

 

 

Fault bucket -696358589, type 1

Event Name: APPCRASH

Response: Not available

Cab Id: 0

 

Problem signature:

P1: Prepar3D.exe

P2: 1.4.4747.0

P3: 50253a53

P4: StackHash_9fa7

P5: 6.2.9200.16578

P6: 515fac6e

P7: c0000374

P8: PCH_3B_FROM_ntdll+0x0002DC34

P9:

P10:

 

Attached files:

C:\Users\Ifikratis\AppData\Local\Temp\WERF492.tmp.WERInternalMetadata.xml

 

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_e17fc4eb9430d4e6557fa41f5c69cc784b516f_17db3c59

 

Analysis symbol:

Rechecking for solution: 0

Report Id: 780981e1-c190-11e2-bebc-902b34da42e2

Report Status: 0

Hashed bucket: e642265aacf6c1a41b845113893d5e54

 

2)

Faulting application name: Prepar3D.exe, version: 1.4.4747.0, time stamp: 0x50253a53

Faulting module name: ntdll.dll, version: 6.2.9200.16578, time stamp: 0x515fac6e

Exception code: 0xc0000374

Fault offset: 0x000daa3c

Faulting process id: 0x1478

Faulting application start time: 0x01ce55992d34cb08

Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D\Prepar3D.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: 780981e1-c190-11e2-bebc-902b34da42e2

Faulting package full name:

Faulting package-relative application ID:

 

 

3)

Faulting application name: Prepar3D.exe, version: 1.4.4747.0, time stamp: 0x50253a53

Faulting module name: g3d.dll, version: 0.0.0.0, time stamp: 0x50253ab4

Exception code: 0xc0000005

Fault offset: 0x0009d64a

Faulting process id: 0x3d4

Faulting application start time: 0x01ce554ed9678071

Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D\Prepar3D.exe

Faulting module path: C:\Program Files (x86)\Lockheed Martin\Prepar3D\g3d.dll

Report Id: 2bc469ec-c143-11e2-beba-902b34da42e2

Faulting package full name:

Faulting package-relative application ID:

 

4)

 

Faulting application name: Prepar3D.exe, version: 1.4.4747.0, time stamp: 0x50253a53

Faulting module name: ntdll.dll, version: 6.2.9200.16578, time stamp: 0x515fac6e

Exception code: 0xc0000374

Fault offset: 0x000daa3c

Faulting process id: 0x664

Faulting application start time: 0x01ce554640ac39ce

Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D\Prepar3D.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: aa97e42a-c141-11e2-beb8-902b34da42e2

Faulting package full name:

Faulting package-relative application ID:

 

 

 

And this is the error from today when crahsed before I reach Barcelona (still ~80nm away) when the problem has appeared and I clicked to open a menu.

It wouldn't have crashed if there was no the shuttering problem.

 

 

Faulting application name: Prepar3D.exe, version: 1.4.4747.0, time stamp: 0x50253a53

Faulting module name: KERNELBASE.dll, version: 6.2.9200.16451, time stamp: 0x50988950

Exception code: 0xe0434352

Fault offset: 0x00014b32

Faulting process id: 0x21bc

Faulting application start time: 0x01ce56f1f1574b05

Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D\Prepar3D.exe

Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll

Report Id: 2e511325-c304-11e2-bec0-902b34da42e2

Faulting package full name:

Faulting package-relative application ID:

HIGHMEMFIX is ignored so it can have NO effect in P3D. The Learning Center will be changed.

 

I seriously doubt that your overclock has anything to do with this but that's your call.

 

The registered version of FSUIPC has a g3dll fix - have you installed that version? If not - do so!

 

Vic

Let me know what you find on the faulting modules ...

For FSUIPC OOM .. just google it .. if you do not find it I will look it up after dinner.

If you have the newest FSUIPC it may already be in use.

 

"Destination scenery is irrelevant as the problem happens way before I reach the airport area, when still in cruise."

 

Well, when you are working the unknowns .. we need to know what is being used.

My thought was .. could Overclocking cause overheating .. some component .. that causes a crash?

So, why not just eliminate it for a few days?