AndrewT

Thiago Baptista said: Just to clarify something: there WERE files in that folder before. I tried restoring them through the operating system (an option under the context menu in Windows Explorer), but the last backup was from three weeks ago.

There's certainly nothing in the game that deliberately deletes saves from anywhere. So i cannot explain what happened to those save files.

...

Read more

Thiago Baptista said: I opened the save game folder in Windows Explorer at %HOME%/Documents/Paradox Interactive/Stellaris/save games and, indeed, the folder was empty?

That is expected as only local saves are written there.

Under Steam a local cache of cloud saves is written here:
C:\Program Files (x86)\Steam\userdata\\281990\remote\save games\

I'm not familiar with how GoG does these things but I'd assume they have a similar location, you may need to contact them if you can't find it. Perhaps a search for *.sav files would find them? ... Read more

Looking at that dxdiag again, this is the problem we’re now seeing with the recent AMD video drivers. Please revert to older ones, say 19.2.x , that should fix it.  

They both work fine for me ... one is Visual C++ 2015, the other DirectX 9.0c

You can also get them in the steam/steamapps/common/steamworks shared/ folders.  

I assume if you run eu4.exe directly, bypassing the launcher, it also fails? If so the issue is with the game not the launcher.


Has the game ever run OK on this computer? Or never?

IF NEVER:
Install ALL these Microsoft modules:

https://www.microsoft.com/en-au/download/details.aspx?id=8328
... Read more

Does running stelleris.exe get you into the game?


Please attach here the three .log files from:
C:/users//AppData/Roaming/Paradox Interactive/launcher-v2/  

Please try this:

- exit the Steam app completely
- uninstall Paradox Launcher v2 from the Windows "Apps and features" utility, if still present.

Delete the following folders if still present:
- C:/users//AppData/Local/Programs/Paradox Interactive/
- C:/users//AppData/Local/Paradox Interactive/
- C:/users//AppData/Roaming/Paradox Interactive/launcher-v2/

- run steam.exe as the Windows Admin user
- run Stellaris from the Steam PLAY button

I hope that works for you!

If not though, try running stellaris.exe directly. Does that at least get you into the game itself?  

Datsmore said: Is there an actual fix for this issue out yet? I have outright disabled windows defender and still cannot accept the EULA.

Disabling AV apps doesn't actually do what it sounds like, you need to actively allow the .exe through. See post #10 above.  

If you feel these issues are essentially game bugs, then you should post them in new threads in the Bug Report forum, with screenshots, videos, the above text files, and whatever else QA might need to reproduce the problem.

Good luck with that!  

I don't see any obvious cause for your problems in those text files, I'm afraid. Both seem to relate to the mouse cursor's apparent and real positions not being lined up right, or rather that in some circumstances that happens whereas in others they line up just fine. Quite bizarre.

What's especially odd is you say you get the gui_scale tooltip issue in Windows too; I must have recommended that option dozens of times to Windows users by now and so far as I know none have seen that effect - I'm sure they would have told me!

Similarly with your issues on Linux; we'd know for sure if everyone got those!

I really don't know what to suggest, in all honesty. There doesn't seem to be any kind of tech tweak we can use to get you past these issues.  

I agree. At this point I think you need developer help, as there doesn't seem to be anything you or I can do to affect this problem for you.

I suggest you make a new thread in Bug Reports, and attach those files from up in post #3. A video of the problem would also be useful I think.

Sorry to have been unable to help you at all so far!  

Miskoosi said: Hey, just made another discovery when looking at afterburner's hardware monitor: my frametime when eu4 is unpaused sits at around 50ms on average. This would explain the hitching. I don't know why the rivatuner is lying and saying its at 6ms. Any idea why it would sit at 50ms?

Sorry, this question beyond my experience and knowledge. But you aren't running the game with Rivatuner active I assume?

And, if you are using GeForce Experience to configure the game's video, try unloading that - any different?

That thread is par... Read more

I see, so this may be an issue with the older Clausewitz games on your rig; quite why I cannot guess!

Weird question - is your video card in the slot nearest the CPU?  

Sorry, really no idea then. Does this affect our similar games CK2, HOI4, Stellaris if you have any of those? CK2 is free to play now, which might be a good test.  

Try changing this line in settings.txt:

refreshRate=60

I don't see a lot else of concern in there. Your D: drive is a little short of free space; are Steam, the Steam library the game is in, and the Windows Documents folder all on the same drive? C: hopefully?  

PillowWhite. said: for macbook 16-in, this does not work, and i cant find the "pdx_settings.txt" in the files btw

Setting it in the game's launcher will edit that file for you. But that file is certainly there, in the Documents/paradox/eu4/ folder.  

Are you OCing anything? Try turning that off if so.

DXDIAG is a program you run from a command prompt or the Windows start menu 'run' dialog box (or 'search programs' in Windows 7 or later). After running it will open a window and start collecting info with a progress bar in the lower-left corner. When it completes click the 'save all information' button and save it to a file then attach that file here.

Please attach your Documents/Paradox/EU4/settings.txt and pdx_settings.txt .
From your Documents/Paradox/EU4/logs/ folder, attach system.log .  

Sorry about that then! How about borderless or windowed modes, any better?  

This is now known to be a bug in the shader compiler in MacOS 10.15.x , I'm not sure it is possible for us to fix it in the games.

Did you try post #2 above? That has worked for everyone I've come across except in post #4 above.  

I don't know why that would be like that for you, as you can see above that generally works for other Mac users.

You are only trying resolutions listed in your system.log file, yeah?