6 hours ago, mikeymike said:

So I did try this and it fixed the problem 

but I’m confused as to why all my icons etc of how windows was set up is not the same.

so this means that my win10 is corrupted somehow on that user account name ?that is causing issues above?

thanks 

mike

Sweet! Good news. This proves that your operating system and P3D installation are perfectly fine.

Now you need to do a little detective work. The problem lies within a file saved in the user's profile. Specifically, a file stored in either the AppData or the My Documents folder. Every user gets their own set of these folders. When you switched users, P3D (and Windows) set up a fresh copy of all of the files it needs to save option settings and scenarios for the new user. Your problem in the other user account clearly lies in a file stored in one of those folders (or a sub-folder). The other piece of good news is that you also generated a fresh, clean copy of whichever file is messing you up in the original account when you logged in and ran P3D under the new account.

An example to see if the problem is in your Prepar3D.cfg file.

1. Rename C:\Users\<Original account>\AppData\Roaming\Lockheed Martin\Prepar3D v5\Prepar3D.cfg file to Prepar3d.cfg.bak
2. Copy C:\Users\<NEW account>\AppData\Roaming\Lockheed Martin\Prepar3D v5\Prepar3D.cfg to C:\Users\<Original account>\AppData\Roaming\Lockheed Martin\Prepar3D v5\Prepar3D.cfg
3. Test P3D in original account.
4. If problem not solved, restore original Prepar3D.cfg file, and start over at step 1 using a different file. 

Good Luck!

EDIT: In the "can't hurt, might even fix the original problem" category. Try this. Go to your C:\Users\<Your_username>\AppData\Local\Temp\ in explorer and delete every file and folder with a create date before today. They are supposed to be temporary, and there is no need to keep them. I got bit by this last week during the Win 10 upgrade.

Edited December 30, 20205 yr by MDFlier

1 hour ago, MDFlier said:

AppData\Roaming\Lockheed Martin\Prepar3D v5

Sweet! Good news. This proves that your operating system and P3D installation are perfectly fine.

Now you need to do a little detective work. The problem lies within a file saved in the user's profile. Specifically, a file stored in either the AppData or the My Documents folder. Every user gets their own set of these folders. When you switched users, P3D (and Windows) set up a fresh copy of all of the files it needs to save option settings and scenarios for the new user. Your problem in the other user account clearly lies in a file stored in one of those folders (or a sub-folder). The other piece of good news is that you also generated a fresh, clean copy of whichever file is messing you up in the original account when you logged in and ran P3D under the new account.

An example to see if the problem is in your Prepar3D.cfg file.

1. Rename C:\Users\<Original account>\AppData\Roaming\Lockheed Martin\Prepar3D v5\Prepar3D.cfg file to Prepar3d.cfg.bak
2. Copy C:\Users\<NEW account>\AppData\Roaming\Lockheed Martin\Prepar3D v5\Prepar3D.cfg to C:\Users\<Original account>\AppData\Roaming\Lockheed Martin\Prepar3D v5\Prepar3D.cfg
3. Test P3D in original account.
4. If problem not solved, restore original Prepar3D.cfg file, and start over at step 1 using a different file. 

Good Luck!

EDIT: In the "can't hurt, might even fix the original problem" category. Try this. Go to your C:\Users\<Your_username>\AppData\Local\Temp\ in explorer and delete every file and folder with a create date before today. They are supposed to be temporary, and there is no need to keep them. I got bit by this last week during the Win 10 upgrade.

Will try this out. And keep you posted 

thank you very much.

mike

3 hours ago, MDFlier said:

Sweet! Good news. This proves that your operating system and P3D installation are perfectly fine.

Now you need to do a little detective work. The problem lies within a file saved in the user's profile. Specifically, a file stored in either the AppData or the My Documents folder. Every user gets their own set of these folders. When you switched users, P3D (and Windows) set up a fresh copy of all of the files it needs to save option settings and scenarios for the new user. Your problem in the other user account clearly lies in a file stored in one of those folders (or a sub-folder). The other piece of good news is that you also generated a fresh, clean copy of whichever file is messing you up in the original account when you logged in and ran P3D under the new account.

An example to see if the problem is in your Prepar3D.cfg file.

1. Rename C:\Users\<Original account>\AppData\Roaming\Lockheed Martin\Prepar3D v5\Prepar3D.cfg file to Prepar3d.cfg.bak
2. Copy C:\Users\<NEW account>\AppData\Roaming\Lockheed Martin\Prepar3D v5\Prepar3D.cfg to C:\Users\<Original account>\AppData\Roaming\Lockheed Martin\Prepar3D v5\Prepar3D.cfg
3. Test P3D in original account.
4. If problem not solved, restore original Prepar3D.cfg file, and start over at step 1 using a different file. 

Good Luck!

EDIT: In the "can't hurt, might even fix the original problem" category. Try this. Go to your C:\Users\<Your_username>\AppData\Local\Temp\ in explorer and delete every file and folder with a create date before today. They are supposed to be temporary, and there is no need to keep them. I got bit by this last week during the Win 10 upgrade.

Can I just copy over the whole app roaming prepar3d folder and documents folder and overwrite?

thanks

mike

Short answer - yes, that will make P3D work under the old user account. If you just want to get flying again in a hurry, do it.

Longer answer - This process can wipe out any changes (control assignments, config changes, addons, etc.) that you made to P3D under your old account, but P3D should work normally even though it will look like a fresh installation.

If it were me... I'd do it backwards. Copy the original user's AppData/Local folder over the new user's AppData/Local folder and see if it broke P3D for the new user. If that works (P3D didn't break for the new user), try copying the old user's AppData\Roaming over the new uses' AppData\Roaming and test again. By process of elimination you can figure out exactly which file or folder is messing up your old login's P3D. If you get lost or mess things up, just delete the new user, create a new new user, startup P3d, and then you'll have a fresh set of files to use in troubleshooting.

Just one more thought. We've been mostly talking about the files and folders in AppData causing your problem. It might be a bad default flight causing your problem. Try renaming your original user's \Documents\Prepar3D v5 Files\ folder to \Documents\Prepar3D v5 Files_saved\ and then copy the new user's Documents\Prepar3D v5 Files folder over to the original user's Documents folder.

Edited December 30, 20205 yr by MDFlier

On 12/27/2020 at 7:13 PM, mikeymike said:

upon restart of P3d I noticed shadershsl got corrupted. 
So I copied the backup I have.

Using a new user account is a long way around simply running "Delete Generated Files". I hope that you did not really overwrite the ShadersHLSL folder.

 

1 hour ago, Reader said:

Using a new user account is a long way around simply running "Delete Generated Files". I hope that you did not really overwrite the ShadersHLSL folder.

 

No i deleted the shadershsl folder then I just pasted the back up original.

Cheers 

mike

5 hours ago, MDFlier said:

Short answer - yes, that will make P3D work under the old user account. If you just want to get flying again in a hurry, do it.

Longer answer - This process can wipe out any changes (control assignments, config changes, addons, etc.) that you made to P3D under your old account, but P3D should work normally even though it will look like a fresh installation.

If it were me... I'd do it backwards. Copy the original user's AppData/Local folder over the new user's AppData/Local folder and see if it broke P3D for the new user. If that works (P3D didn't break for the new user), try copying the old user's AppData\Roaming over the new uses' AppData\Roaming and test again. By process of elimination you can figure out exactly which file or folder is messing up your old login's P3D. If you get lost or mess things up, just delete the new user, create a new new user, startup P3d, and then you'll have a fresh set of files to use in troubleshooting.

Just one more thought. We've been mostly talking about the files and folders in AppData causing your problem. It might be a bad default flight causing your problem. Try renaming your original user's \Documents\Prepar3D v5 Files\ folder to \Documents\Prepar3D v5 Files_saved\ and then copy the new user's Documents\Prepar3D v5 Files folder over to the original user's Documents folder.

So I did try above mentioned in first paragraph but to no avail I did have just to reset my control assignments that’s all.

but as for default flight I will have to try that  documents folder copy.

I’m just confused as to why when  I generate a new P3d Cfg everything is fine 

but when I restart the sim the text is overlapping.

i will report back.

cheers 

mike

Edited December 30, 20205 yr by mikeymike

On 12/30/2020 at 5:51 AM, MDFlier said:

Short answer - yes, that will make P3D work under the old user account. If you just want to get flying again in a hurry, do it.

Longer answer - This process can wipe out any changes (control assignments, config changes, addons, etc.) that you made to P3D under your old account, but P3D should work normally even though it will look like a fresh installation.

If it were me... I'd do it backwards. Copy the original user's AppData/Local folder over the new user's AppData/Local folder and see if it broke P3D for the new user. If that works (P3D didn't break for the new user), try copying the old user's AppData\Roaming over the new uses' AppData\Roaming and test again. By process of elimination you can figure out exactly which file or folder is messing up your old login's P3D. If you get lost or mess things up, just delete the new user, create a new new user, startup P3d, and then you'll have a fresh set of files to use in troubleshooting.

Just one more thought. We've been mostly talking about the files and folders in AppData causing your problem. It might be a bad default flight causing your problem. Try renaming your original user's \Documents\Prepar3D v5 Files\ folder to \Documents\Prepar3D v5 Files_saved\ and then copy the new user's Documents\Prepar3D v5 Files folder over to the original user's Documents folder.

Could it be chaseplane cameras causing the scaling effect with red text menu being overlapped by drop down menu?

thanks

mike

Edited January 1, 20215 yr by mikeymike

I have tried everything mentioned above and nothing 

even tried older drivers, the cfg scaling somehow gets corrupted upon restart of sim after new cfg has been created it’s fine. 
I then restart sim and get the menu overlapping the text for some reason.

cheers 

mike

Nvm figured it out 

Wow.. just wow

mike