Merry Xmas everyone,

Last week i tested an new Nvidia RTX 3080, but i decide to stay with my rtx 2080ti (11GB), because the 3080 only had 10 GB and i got dxgi errors on heavy sceneries.

Because i noticed the last days heavy studders, i created this morning a new prepare3d.cfg.

Now i have two entrys, the 2080 and the 3080 Graphiccards. And the additional entry Jobscheduler 364.

I deleted the entrys multiple times,  i deleted the hole cfg two times and let the CCleaner clean the registry. But the next time Prepare 3d created new entries from the 2080, 3080 and the Jobscheduler.

My System is an Intel i7 8086K, RTX 2080ti, 32 GB, HT off.

Thanks for any help

Joachim

 

57 minutes ago, Prisco said:

Merry Xmas everyone,

Last week i tested an new Nvidia RTX 3080, but i decide to stay with my rtx 2080ti (11GB), because the 3080 only had 10 GB and i got dxgi errors on heavy sceneries.

Because i noticed the last days heavy studders, i created this morning a new prepare3d.cfg.

Now i have two entrys, the 2080 and the 3080 Graphiccards. And the additional entry Jobscheduler 364.

I deleted the entrys multiple times,  i deleted the hole cfg two times and let the CCleaner clean the registry. But the next time Prepare 3d created new entries from the 2080, 3080 and the Jobscheduler.

My System is an Intel i7 8086K, RTX 2080ti, 32 GB, HT off.

Thanks for any help

Joachim

 

Just delete the whole Prepar3d folder in AppData/roaming/Lockheed Martin/ and try running the sim again then adjust settings and exit and edit back in to prepar3d.cfg

[JOBSCHEDULER]

AffinityMask=364 

Assuming you can see the AppData folder.

Can i ask why 364 and not 255 since there's no HT active?

36 minutes ago, 40track said:

Just delete the whole Prepar3d folder in AppData/roaming/Lockheed Martin/ and try running the sim again then adjust settings and exit and edit back in to prepar3d.cfg

[JOBSCHEDULER]

AffinityMask=364 

Assuming you can see the AppData folder.

Can i ask why 364 and not 255 since there's no HT active?

Also could any add on scenery be regenerating it?

Try deleting the config and the run the Delete Generated Files in the main P3D install then restart.

Thanks for your tips.

I uninstall the Nvidia Driver via DDU and install the newest, but still the same error.

@40Track: that didn't solve the problem. i didn't wrote a Jobscheduler in the cfg. its p3d by himself, who writes the entry. I change now manually to 255.

@G-RFRY: Running Delete Generated Files, i mean that i've read, it may make many Problems after running?!

2 minutes ago, Prisco said:

Thanks for your tips.

I uninstall the Nvidia Driver via DDU and install the newest, but still the same error.

@40Track: that didn't solve the problem. i didn't wrote a Jobscheduler in the cfg. its p3d by himself, who writes the entry. I change now manually to 255.

@G-RFRY: Running Delete Generated Files, i mean that i've read, it may make many Problems after running?!

Keep an eye on it. If it reverts to 364 again replace the drive ASAP as the drive has been fried with the old info on it.

what does it mean replace the drive? to buy a new one?!

26 minutes ago, Prisco said:

what does it mean replace the drive? to buy a new one?!

Yes. ONLY if the 364 number comes back as the drive would be damaged. BUT ONLY IF IT DOES IF THE 255 edit stays you're ok. 

3 minutes ago, 40track said:

Yes. ONLY if the 364 number comes back as the drive would be damaged. BUT ONLY IF IT DOES IF THE 255 edit stays you're ok. 

Also run a scandisk to see if any errors on the drive appear then make sure the 255 stays after reboot. if 364 reappears then you'll have to format OR worst case replace drive.

The entry 255 stays after restart the P3D...... sweat...😅

i think its a strange Problem, who is resposable for the entries, i'd never made?!

Good

10 minutes ago, Prisco said:

The entry 255 stays after restart the P3D...... sweat...😅

i think its a strange Problem, who is resposable for the entries, i'd never made?!

Good it holds. You'll be ok for now. If it reoccurs consider formatting drive and clean install. Then diagnose from there.

21 minutes ago, Prisco said:

The entry 255 stays after restart the P3D...... sweat...😅

i think its a strange Problem, who is resposable for the entries, i'd never made?!

Just a heads up on the affinitymask change the 255 to 5592405 leaving HT off. bad math on my side.

6 minutes ago, 40track said:

255 is fine. Just had to recheck.

Try AffinityMask=63  Just confirmed thread miscount. Sorry about that.

It looks more like a simple permissions issue with Prepar3D.cfg. I read some alarming suggestion, the file can simply be deleted. None of the additions will do any real damage but the suggested solutions will.

I am using Simstarter and i think, iwill contact Pero. Maybe, he knows a solution.