Bugs in v1.10 to be fixed in v1.11

[Sinjen]

I had 2 fully loaded transport TF's sail right up to Gilli Gilli with a spotted Japanese Carrier TF sitting a few hexes away from their path to and from it. Needless to say. I lost 19 ships and most of the 3rd Australian Division in 1 day because the Retirement for TF's isn't working.

I have now stopped playing UV until a patch can be released for this. In its current state its unrealistic and unenjoyable to play due to the inability of TF's to retire when they should.

Another gamebreaker is also the fact that Tokyo Express and Night Bombardments no longer retire but instead sit at their target hex the whole day which totally screws them and exposes them to air power.

My opponent stated to me that his transport TF's were not retiring from my spotted night bombardment group which ended up sitting at Lunga all day while his transport TF's sailed in obliviously into the port and were destroyed. He lost 23 ships in one day to my one bombardment group that should have retired that night after bombarding but instead sat in lunga harbor as a surface action group until I gave it the order manually to return to homebase. His TF's should have retired from my surface action group rather than sailing into Lunga and laying anchor while my cruisers methodically destroyed them.

Another annoying bug is the fact that Transport TF's no longer return to their homeports when they are done unloading. While this is not a gamebreaker. It adds more micromanagement and puts your transport TF's in harms way that much longer than they need to be on the front line bases.

Also both players see a message whenever the computer creates a sub TF. XXXX sub is unable to load torps from brisbane or SS-Gato is loading 10 mines into tubes. When in reality the next turn I checked the Gato and it was fully loaded with torps and set to sub patrol and not mine. Either way my opponent seems to know anytime I get a new sub in the game if I let the computer control sub TF's.

Myself and all my strategic minded friends love this game. We really want to play it. Most of us restarted our PBEM's when the new patch came out. Some of those were already into 1943. We have tried to spread the word about this game to all our friends, but find ourselves reserved in doing so until these bugs are fixed.

Thanx and I hope these will be fixed asap so we can all get back to praising the makers of UV and the soon to be WITP.

[Enforcer]

I am the opponent Sinjen is speaking of and I have to say that I understand there will be bugs in a game, but when the corrections make you have to restart a game that has went 7 months it kinda pisses me off!!
Now we are 1 month into the new game and AGAIN we will have to start over.....this gets old QUICK and a few more of these RESTARTS will make me want to shove this game on the shelf for a while!! which I dont want to do, but then again I dont want to restart everytime something is wrong...

I dont need a reply to this from 100 experts!! only from the Matrix staff....

[Marc von Martial]

Old saves and PBEM games _will work_ with UV 1.10 provided all players update at the same time. However, any 1.10 OOB changes will only be included in games that are _started_ with 1.10. Once you upgrade to 1.10, all PBEM passwords will also be seamlessly encrypted.

[Enforcer]

Yes I understand It will work ..but in the case of the one we just started becuase of this bug, sinjen lost 19 ships in one day!!! now I also lost 23 ships...I will still play , But I dont think he will!!
What pisses me off is in the initial carrier battle (shokaku,zuikaku vs. lexington,yorktown) ... I smashed him lexington and yorktown sunk and zuikaku with only 21 sys damage. Now because of this bug I LOSE THE CHANCE TO FINISH THIS GREAT GAME.....

I get tired of the... "we found another bug" issue.. the playtesters should have found this issue when playtesting the patch!!! I mean the bugs jumps out at you ...how can you not catch it!!!

Now this makes the second game in a row we have to have a "DO OVER"... and frankly it makes me not want to tell my buddies about this game at all, I dont like catching flak from freinds who have spent money on a buggy game.

[Erik Rutins]

Gentlemen,

I understand your frustration. However, all of these retirement problems are actually one bug (albeit a biggie) that crept in despite 50+ others being fixed. There is no litany of bugs that slipped through here. There is also nothing preventing you from waiting perhaps another day or so for the correction (which we are working on at warp speed) and then just picking up your game from a few turns back.

As for how it could not be caught... if you have not playtested, you may not realize that patches go through many builds. This bug did not exist in the vast majority of them. As far as we can tell, it slipped in a day before release and was not caught in the very last wave of testing.

If you look at any game, you'll find patches fixed some bugs and that let another bug in. Most companies in my experience wait until the next major patch to fix such problems. We finished 1.10 over the weekend, released it and started working on 1.11 to fix this bug on Monday. It's now noon on Wednesday and we're darn close to a good 1.11 release candidate. UV has been one of the most stable, bug-free releases of a new engine and design that I've seen in a long while and we're in this for the long haul. It will only continue to get better and more bug-free.

Regards,

- Erik

[Sinjen]

Erik,

Thanks for the reply. I am eagerly awaiting the patch.

-Sinjen

[Hartmann]

Originally posted by Sinjen
Erik,

Thanks for the reply. I am eagerly awaiting the patch.

-Sinjen

Seems like the fix will arrive very soon!

Erik: I'm really sorry for the crew that this ugly "no retirement" bug slipped in last minute to leave a stain on an otherwise great patch. This was extreme tough luck and totally undeserved. (Well, just wanted to let you know that we all know that. )

Hartmann

[elmo3]

As someone who has been a playtester for years, on a number of titles including GG's BTR, I agree with Erik. It is inevitable that, no matter how hard the testers try, something will slip through. That Matrix is working to put out a quick fix for this problem shows a high level of commitment and it's appreciated.

[wmtiz]

I agree as well. I know from experience writing code that when you are adding code to fix one thing, the very act of the code changes can open doors for potential bugs that were closed before. Be patient. The main structure and code base for this game is very solid, especially when you consider the complexity of the calculations that have to be involved during each game turn or phase.

Other game genres have experienced bug-riddled games at release in recent months. Anyone into RPGs? Anyone who bought Pool of Radiance last year knows first hand how buggy things can get, some poor people tried to uninstall the game because of its extreme bugginess only to find the worst bug of all, corruption to certain sectors/tracks on their hard drive that resulted in a need to completely reformat the hdd and reinstall their OS. Ouch!!!

This game is one of the most stable games I have purchased in the past three years and it is by far number one in the designers quickly addressing issues that are pointed out by the players.

Bravo to the developers for their commitment to making this game as good as it can be!

[BillBrown]

and while we are on this subject, how about Wizards and Warriors? the producers would not even put out a patch to fix the bugs!! the only patch was an unofficial one.

It is an unfortunate fact that bugs do infest software projects and some are there but are not seen because other parts of the program obscure them. when a bug is fixed, often others appear.

Matrix is doing excellent work to fix problems/bugs AND enhance the product( don't forget patch 1.10 added functionality and fixed bugs).