I think he's referring more to a change in the general policy of "peek-a-boo, we've got a patch for you!"
-
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
Has anyone found a workaround for the carrier bug that lets older carriers be better than newer ones? Its crimping my game badly. I think its worth a second hotfix for it.
The Starfox said:
Not as far as I read, we still will have to wait. Should not be much longer, I hope.
Well, it is possible to go around it, but effectively only in MP, just disable CAG upgrading, when new model is out build it, deattach and disband old one, attach new one.The Starfox said:
The Starfox said:
After weeks, the hoftfix would already be very cold
I agree that a quick hotfix should have been given to us, but the last hotfix was somehow a tragedy: P'dox wanted to do us a pleasure (my interpretation of things) to give us the hotfix right before easter. And got flamed beause the hotfix was onlyhot, but no fix.
Many (qualified) complaints, but also much posts that were really somewhat between insulting and idiotic vs. P'dox.
So my guess: We won't see many hotfixes in the future, only patches. Which are never late, nor early...
Anyway, like I said before: Another Hotfix should have been given to us, even on the risk that is still has some bugs - or some new bugs.
- The hotfix did fix several issues, but not everything.Long Lance said:After weeks, the hoftfix would already be very cold
I agree that a quick hotfix should have been given to us, but the last hotfix was somehow a tragedy: P'dox wanted to do us a pleasure (my interpretation of things) to give us the hotfix right before easter. And got flamed beause the hotfix was onlyhot, but no fix.
Many (qualified) complaints, but also much posts that were really somewhat between insulting and idiotic vs. P'dox.
So my guess: We won't see many hotfixes in the future, only patches. Which are never late, nor early...
Anyway, like I said before: Another Hotfix should have been given to us, even on the risk that is still has some bugs - or some new bugs.
- It's been said they're working on another patch at the moment.
Shadow86 said:
Both is correct and not new. But doesn't change the fact that another hotfix would have been very appreciated.
Long Lance said:
Exactly. We're now 25 days out from the original "Hotfix" that should've fixed at LEAST the CAG bug.
We've now been waiting since April 5 for a fix to the expansion pack that they charged for in the first place and still haven't repaired. I'm sorry, but that's an obscene amount of time to wait for a fix to a major game issue.
One of the reasons that I peruse the Paradox boards and support their products and not others is that they've always been so responsive to issues like this and in supporting their products. This has just been a sad, frustrating and sobering experience for me.
Truth be told all the reports of the CAG bug appeared after the hotfix, not before.kbromer said:
Borsook said:
Sorry, my post wasn't clearly worded.
It's still been 25 days that the CAG bug has been outstanding SINCE the hotfix, more than enough time to fix an error rather integral to the mechanics of the game.
kbromer said:
I believe I discovered the bug (for myself) before the hotfix. Nevertheless ... it has been a very long time, as kbromer notes. I suspect that the "new" development team that put together the patch created such a tangled mess that it is taking a long time to unravel it. But that's pure speculation. I have historically been a "fanboy" for Paradox support, but I am currently ... feeling moderately peeved.
Last edited:
They're probably trying to eliminate as many bugs as possible in one shot with the patch currently in development, plus reviewing everything so that it doesn't come out as badly as Armageddon did. I'd rather have a full patch than a rushed hotfix to (briefly) please the masses.
Many people want something now, but then whine when the company rushes things and releases them half-baked.
So, on the whole, all I can say is: patience.
Many people want something now, but then whine when the company rushes things and releases them half-baked.
So, on the whole, all I can say is: patience.
Shadow86 said:
i do not know if i should cry or laugh. still patience, fan boy's, paradox-praising after this completly disaster.
don't forget, we're not speeking about a new game, it's about a booster pack which was broken to let's say a third, for most people that bought it for naval combat it's completly broken.
and all we've got, was a short post from johann (at least it was the login of johann) that they are working on bugs.
so come one, wake up. it's all about making profit with less afford, not about making you happy :rofl:
The Starfox said:
there are atleast, that i know of two ways:
1. Dont upgrade them, when you have researched lvl 4 carriers 1938 tech Save. Edit in save, all old cags to lvl 4 cags.
2. Edit inc files so all starting CV has lvl 4 cags instead of lvl 1-3. It's only UK, Japan, USA and the the french Bearn. So it doesnt take long. It will give CV countries an added benefit from 1936 - 1938. But i think it is marginal if you play more or less a historically timeline.
When you research lvl 5 1941, you could again edit save again. But i just put them on do not upgrade.
Just search for carrier in files and edit brigade_model to 3. that corresponds to improved CV cag lvl 4. Models start with model 0.
More than twice, and they always fix it.Gobling said:
I'm not praising anyone here. Call me whatever you want, but that's what I think they should be doing, given they took quite a hit to their image with Armageddon: if they don't fix the mess, it's them who'll ultimately take most of the damage (you lose five fricken' bucks, they lose customer confidence and sales).theissi said:
Oh, and I've said it and I'll say it again: more whining won't make the patch come any sooner. Do something else to entertain yourself.
Gormadoc said:
Perhaps I have an idea that's a good workaround. Make new Carrier-Techs not activate new CAGs, but instead imrpove the stats for CAGs.
For every new Carier level researched, one could get these bonusses (surely needs some tweaking, didn't try it):
command = { type = max_organization which = cag value = 2 }
command = { type = naval_attack which = cag value = 3 }
command = { type = air_attack which = cag value = 2 }
command = { type = air_defense which = cag value = 1 }
command = { type = max_positioning which = carrier value = 0.03 }
command = { type = min_positioning which = carrier value = 0.03 }
No range bonus, but positioning bonus. One would only need to change CV tech tree ONCE by c&p and delete the lines with
command = { type = new_model which = cag value = X }
No ICdays for upgrading, but that's the same for all.
Max firing distance can't be change by event commands, at least I didn't find anything in the event commands.txt.
applauseapplauseapplause
:wacko: ???
ahh, that's actually rather clever, as supposedly its possible to change brigade stats (at least, the editor allows it to happen...)
Long Lance said:Perhaps I have an idea that's a good workaround. Make new Carrier-Techs not activate new CAGs, but instead imrpove the stats for CAGs.
For every new Carier level researched, one could get these bonusses (surely needs some tweaking, didn't try it):
command = { type = max_organization which = cag value = 2 }
command = { type = naval_attack which = cag value = 3 }
command = { type = air_attack which = cag value = 2 }
command = { type = air_defense which = cag value = 1 }
command = { type = max_positioning which = carrier value = 0.03 }
command = { type = min_positioning which = carrier value = 0.03 }
No range bonus, but positioning bonus. One would only need to change CV tech tree ONCE by c&p and delete the lines with
command = { type = new_model which = cag value = X }
No ICdays for upgrading, but that's the same for all.
Max firing distance can't be change by event commands, at least I didn't find anything in the event commands.txt.
applauseapplauseapplause
That sounds to be very good!!
You don't have to delet lines, just put "#" in front so you can remove.
That might be a temp hotfix until the next patch ist arriving.
Test?
- Status