• 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.
Status
Not open for further replies.
WAD. It prevents air units from rebasing to the opposite side of the world in a single day. When organization is negative, you cannot perform any action (also meaning that if the province is taken, the air units cannot flee and get destroyed).
 
I don't know if this is the correct place to ask this, but I remember a while ago that Lennartos mentioned something about changing the supply system to take into account that for example you can not supply a huge army with just one port. Has anything in these lines been work on on the patch?
 
Have the CTD's when attacking been fixed?
 
Complete Changelog of 1.05B4
(...)
Implemented Support # 953 : Moddable max number of attachment for each naval unit type
(...)

Does this also mean that we can now mod in the ability to add more than one brigade to our divisions? ;)
 
CTD when reloading savegame

Playing GC 36 as GER. I saved on June 16 1936, cause I don´t want a situation where SCW is taking forever. So I reloaded (without leaving the game). When June 17 came up the game crashed. I quit the game and started anew. First time June 17, no problem. Reload, then June 17 and CTD again. This has never happened in any version before. Running old P4 with 2 GB and Windows XP, normal resolution (never changed that).

Edit: I installed 1.05 beta 4 on a 1.04 version. Looks like the problem is gone (playing US this time). Maybe you shouldn´t install beta 4 on beta 3...

Edit 2: Nope, wrong again. I had a CTD right after saving the game on July 17 1936 at 0:00 and letting the game continue; sigh
 
Last edited:
Occasionally I am still experiencing the same problem attacking enemies (unknown string wanted) in 27378972 days from now (or do I have to start a completely new game?)

I still have the problem with a clean v1.05 and a new game.
That time, before unknown string, i had an error message in a system window: LastDate was not valid Line 61.

I was attacking with a US stack italian army while Uk was already launching attack. GC36
 
Playing GC 36 as GER. I saved on June 16 1936, cause I don´t want a situation where SCW is taking forever. So I reloaded (without leaving the game). When June 17 came up the game crashed. I quit the game and started anew. First time June 17, no problem. Reload, then June 17 and CTD again. This has never happened in any version before. Running old P4 with 2 GB and Windows XP, normal resolution (never changed that).

I think that you have the same problem like me.
I didn't test another country or scenario as Germany 1936, maybe someone has the same problem with another country?
 
Last edited:
Vanilla 1.05, this time it took only two weeks to reach timeglitch with unknown string wanted and few days later CTD after attempting to issue any kind of order.
 
I still have the problem with a clean v1.05 and a new game.
That time, before unknown string, i had an error message in a system window: LastDate was not valid Line 61.

I was attacking with a US stack italian army while Uk was already launching attack. GC36

3 Reports and only one reported the all important check i made in B4 ;)
Line 61, ok... very strange indeed
 
2 Reports Line 61..ok

EDIT:
1) Does this bug appear if the game has not been saved?
2) Does this bug only appear after using strategic redeployment
 
Last edited:
I played a bit as Republican Spain earlier and can say I had ZERO problems now (which includes crashes AND the armies-won't-attack bug). Granted, I only played for a few months, but before I'd crash constantly, so something must have changed (for the better). Using Windows 7 Professional 64-bit if you recall. Good job.

Edit: I can confirm peace_with_all works perfectly now and does NOT force peace upon the entire alliance. Thank you so much! :)
 
Last edited:
Confirmed with GC36 Cuba.
Good way to remove old guard leaders! :eek:

Playing GC 36 USSR. When I disband a stack of units (or a single unit) its assigned leader disappears never to be seen again. This is true even for leaders that haven´t arrived yet. They are no longer available or shown under the leader columns.

Leader "Captured" when unit is created and disbanded before 1 day elapsed fixed ;)
 
Somebody needs to remember to go into scenarios/1936/USA

and do a search and replace "naval_fire_control_" with "naval_fire_controll_".

There are ten of them. OEQO will remain unchanged.

But the right way to do it is to change all "controll" for "control" for every nation file plus including the brigade file or this ain't never gonna go away. It will just keep happening every time somebody makes a new mod or changes the scenario files unless it is done right.

When an upgrade is available for a production and that production had for the moment produced zero, this message will re-appear each time a new tech is found.

I guess it's not WAD.


Fixed and Fixed
 
I don't know if this is the correct place to ask this, but I remember a while ago that Lennartos mentioned something about changing the supply system to take into account that for example you can not supply a huge army with just one port. Has anything in these lines been work on on the patch?

No, im afraid not...
I have just been working on AI + 1.05 patch
 
Status
Not open for further replies.