I think I will test, that's a good idea. With regard to the Linux version if its reasonably playable on all the major distros I could just do that and still host it on the SDD.
can u turn off the restart after exiting a campaign?
- Thread starter 1nf3ct3d
- Start date
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
I think I will test, that's a good idea. With regard to the Linux version if its reasonably playable on all the major distros I could just do that and still host it on the SDD.
The precise point is you wouldn't be doing fine in 1.14 in all cases. Like I already said, I understand the frustration expressed in this thread and it's definitely going to reach Wiz' attention.
- 3
Would exiting to menu take that much longer in 1.14 compared to 1.13? Because I'm not sure if it's WAD, but even clicking "back" after clicking load game and remembering that that's not the game you intended restarts the entire thing.
Just thought I'd add to the conversation to state that I like the change. Having EU4 crash everytime I would select to go back to menu was extremely frustrating, so I'd prefer it if this change was kept in the game. It wouldn't hurt for their to be an option to turn this behaviour off for people who don't like it though.
- 2
I think this is probably the most agreeable compromise for everyone available. Those who want it, keep it. Those who don't, uncheck the option.
- 2
Holy crap! May God have compassion of your boss and company.
Last edited:
- 1
All I see is an unnecessary rant in this thread. Then again, my eyesight isn't the best...
- 6
- 1
Surprinsingly enough, old salts say it is more stable than ever. There are some scary stories they tell every now and then.
Did you notice EU is version 4? Well, PDX somehow managed to live this longer. Of course, only recently they became mainstream.
- 1
- 1
If you need 6-12 months to fix it, maybe it's time to hire some good developers? There are some magical stuff like profilers that might help BTW, and I'm sure many people would love to be interns for you.
- 1
When you're ready to return to reality we can have a fruitful discussion. Notice that I didn't reply to some of the ranting in this thread already because of how it's entirely about things people imagine. Implying we're not using profilers is kind of hilarious.
- 10
- 3
I don't think anyone is suggesting that there isn't a problem with the gamestate not properly resetting, so obviously you wouldn't be 'doing fine in all cases', irrespective of version honestly, without this fix. However, what I think is very clear is people are saying that the solution used to fix the problem is causing as much, if not more, disruption and inconvenience than the problem that the solution fixed.
In fairness mate you can't come up with a crazy notion like 'It's this or spend 6-12 months fixing the problem' and then argue that people have to come 'return to reality' to have a fruitful discussion. You invited a certain level of hyperbole with that comment.
The issue here is fairly simple. There has been an ongoing problem affecting the game since release regarding the gamestate of successive games maintaining their consistency across a number of restarts within the same launch of the application. The devs solution to this, in 1.14, has been to forcibly close and reopen the application in every circumstance where a player might or will be restarting a game. This is an unnecessarily invasive and burdensome fix to a very minor issue that has had, until this point, limited impact.
- 10
His choice of wording, not mine. If we left this out restart, all else being equal, it would CTD most of the time in 1.14.
The crazy part was mentioning it here without being at liberty or it being useful to elaborate on why it is like that (profoundly technical). You're entirely right that post should have had a different direction since little relevant discussion has come of it.
You're mistaken in believing it had minor impact (hint: maintenance effort in keeping it working). The amount of resources this feature consumes is entirely disproportional to its comparative utility. I.e. those for whom resigning is not the most fun part of the game have suffered in secret.
Last edited:
- 1
Just out of curiosity, how about Load Game from within an ongoing game? Does that not have the same issues or should we perhaps expect that to cause a restart in the future as well?
Valid question. It uses somewhat different logic and not all of the issues I listed are present. We decided to keep it like it is despite some issues overlapping. If you want a 100% "pure" load without side effects, you always need to start game from fresh at the moment.
Last edited:
- 3
I'm happy with the restart on exit to menu, as I used to get crashing quite a bit. Wish there was a way to regenerate the RWN without the restart though.
- 7
- 1
If you aren't going to change this behaviour (which with your, @Chaingun, attitude, you aren't), wouldn't it at least been possible to add a „Quit to Desktop“ button to the country selection screen? So that those who decided not to play for any reason wouldn't be forced to restart the whole thing. A band-aid solution, but not worse that we got yesterday.
Anyway, the best course of action would've been to revert to pre-1.14 behaviour that at least wasn't invasive. A man can dream though.
Anyway, the best course of action would've been to revert to pre-1.14 behaviour that at least wasn't invasive. A man can dream though.
- 3
We could consider that GUI change, sure. Wiz/Johan make the calls though.
Revert is unfortunately tied with all other game logic, and we will not be reverting Cossacks. Might be possible to get working well enough again to offer it as an option, as people already suggested.
As for attitude, if you had full insight on this code yours wouldn't be different I can guarantee.
Revert is unfortunately tied with all other game logic, and we will not be reverting Cossacks. Might be possible to get working well enough again to offer it as an option, as people already suggested.
As for attitude, if you had full insight on this code yours wouldn't be different I can guarantee.
I've no idea how much difficulty it presented to the developers, and I should have been more specific in that I was only referring to the user-end of things.
There's no legitimacy to any argument that forcing everyone to restart every time you need to exit to menu is superior to a more limited number of players needing to restart some of the time. That's prima facie. Not that I don't feel sorry for those folk who suffered CTDs mind you, but this is a drastic solution to that problem.
If it's true that adding more content and fixes without this forced restart will result in an increasingly unstable engine then it sounds like Paradox has hit the upper limit of what the game engine can handle given its underlying flaw. It will be extremely interesting to see if more expansions are released before that flaw is fully fixed (and the forced restart doesn't really count as a fix given that it simply attempts to avoid the problem).
- 2
Not so much the engine in this case as the fact EU4 inherits code from EU3 and earlier. Might respond to more later, I should really get some work done today and forum arguments can take a lot of time. 
There is a simple (possibly slightly evil) genius to this. "Have you tried turning it off and on again? Actually, we'll just do it for you. You're welcome."