Hi, anyone else having issue at FSDT KORDV2 with chaseplane? 

I have noticed going in and out of avatar mode ,reenable chaseplane switching views etc was to much for my system. 

Max 8gb VRAM was used latest drivers and around  600gb free space on c drive.

1080ti 11gb

Thanks Michael Moe 

41 minutes ago, Michael Moe said:

Hi, anyone else having issue at FSDT KORDV2 with chaseplane? 

I have noticed going in and out of avatar mode ,reenable chaseplane switching views etc was to much for my system. 

Max 8gb VRAM was used latest drivers and around  600gb free space on c drive.

1080ti 11gb

Thanks Michael Moe 

Can you monitor your VRAM usage? You sure you exhausted it?

S.

23 minutes ago, simbol said:

Can you monitor your VRAM usage? You sure you exhausted it?

S.

Hmm thats new to me simbol. I use a 4k 49" tv at 25hz.

Wasnt aware of a monitor maxload? 

First time i got the _hung_error which sometimes might be driver related so i tried 2 different drivers .

Last error was a OOM message like the old days but seems to be to low swap file i guess. Havent seen this after a SSD 1TB windows drive installation 

Thanks Michael Moe 

Edited October 31, 20196 yr by Michael Moe

In this case 'monitor' means to watch the VRAM usage, not related to a video monitor at all.

35 minutes ago, pgde said:

In this case 'monitor' means to watch the VRAM usage, not related to a video monitor at all.

Ahh okay 😉👍. Well yes i used a VRAM monitor 8300mb maxload but Around 6300mb at crash 

Michael Moe 

2 hours ago, Michael Moe said:

Ahh okay 😉👍. Well yes i used a VRAM monitor 8300mb maxload but Around 6300mb at crash 

Michael Moe 

Then it is not VRAM OOM.

The crash was due to something else..

S.

Never had any issue before but I’ve recently developed a CTD at KORDv2.  Sometimes right at spawn, sometimes a couple minutes afterwards, and always eventually upon approach I get a CTD.

 

No Chaseplane though.

Open up the Event Viewer an look what module specifically caused the sim to crash. Takes some guesswork out of it.

Thanks

i am having this one:

Program: Prepar3D.exe
Framework-version: v4.0.30319
Beskrivelse: Denne proces blev afsluttet pga. en ubehandlet undtagelse.
Undtagelsesoplysninger: System.OutOfMemoryException
   ved UIInterface.HLABridge.!HLABridge()
   ved UIInterface.HLABridge.Dispose(Boolean)
 

svchost

7360,R,98

TILEREPOSITORYS-1-5-18:

C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log

-1023 (0xfffffc01)

 

 

 

Thanks

Michael Moe

Its not the scenery itself,

Just tested with a fresh P3D.cfg and without ASP4 and REX EF , no issues even with Geforce Experience recording in 4K

Michael Moe

Edited November 1, 20196 yr by Michael Moe

Update:

I took a "stress test" in the ORBX Lancair with GTN750 installed flying with DD Chicago and KCGX ORBX installed with autogen maxed out and no issues what so ever.

I think a clean P3D.CFG did it. Maybe its the scenery draw distance (64.000) which makes the system crash.

Overall FSDT KORD is a blast and performing very very well with DD along as well

Thanks

Michael Moe

Edited November 1, 20196 yr by Michael Moe

Glad to see you got it sorted, Michael. Indeed the first thing when troubleshooting P3D is to delete configuration files. Those shoddy tweaks can cause a havoc.

1 hour ago, Evros said:

Glad to see you got it sorted, Michael. Indeed the first thing when troubleshooting P3D is to delete configuration files. Those shoddy tweaks can cause a havoc.

Yeah but i have it back again with the FSL A319-X this time,

Maybe 4K resolution is just to much to ask for my system with these 2 giants on the same page 😄

Michael Moe

42 minutes ago, Michael Moe said:

Yeah but i have it back again with the FSL A319-X this time,

Maybe 4K resolution is just to much to ask for my system with these 2 giants on the same page 😄

Michael Moe

It could be, but I don't really want to go with this option until we have exhausted other ones. Lets start with you posting proper Event Viewer error. The one you posted previously doesn't seem to be properly formatted and is missing some crucial information.

Open Event Viewer and from the 'Summary of Administrative Events' open 'Error' drop down menu. From there, duble click on 'Application Error' (Event ID 1000). From there, look up your latest entry containing Prepar3D.exe and that is probably your latest crashed session. If you select it, then general information becomes available, and that is what you should paste here. I'll post an example below.

Faulting application name: Prepar3D.exe, version: 4.5.13.32097, time stamp: 0x5d8abf93
Faulting module name: util.dll, version: 4.5.13.32097, time stamp: 0x5d8ac1b9
Exception code: 0xc0000005
Fault offset: 0x0000000000026137
Faulting process id: 0x38c
Faulting application start time: 0x01d58dc63d2a83b5
Faulting application path: D:\Prepar3D\Prepar3D.exe
Faulting module path: D:\Prepar3D\util.dll
Report Id: b751fc6e-034b-433a-a398-78e29e3b8d10
Faulting package full name: 
Faulting package-relative application ID: 

You can also use third party log viewers; AppCrashView seems to be popular choice around here, but I don't find it necessary if same thing can be achieved with built-in facilities and full error stack is not needed.

Edited November 1, 20196 yr by Evros

Deleted.....

Edited November 1, 20196 yr by pgde