Jump to content
3000AD Forums
Sign in to follow this  
Supreme Cmdr

UCAWA 1.00.14 Patch Released

Recommended Posts

Single Player

UCAWA.exe = created: Tuesday, Oct 18 2005 1:08 a.m.

modified: Thursday, April 13 2006 1:14 am

UCAWAMP: = same

I followed the directions at the top of this page exactly. I have not attempted the D2D again. I have noticed that no matter what I do, the updater does not download any version of a patch other than 1.00.14. When I installed .08 from the original download, the updater downloaded .14. If I roll the ini file to .12, it does not download a .13 but goes directly to .14

That top post seems to indicate that this would be the case if the version was higher than 1.00.07 so I don't see a way to grab the .13 patch and, indeed, I've never seen that patch come through when I've run the updater.

My system information page gives me the following statement:

"Processor x86 Family 6 Model 7 Stepping 1 AuthenticAMD ~1302 Mhz"

DXDIAG says this:

"Processor: AMD Duron Processor, MMX, 3DNow, ~1.3GHz"

If the second one is correct, I'll be pleased to update it.

Share this post


Link to post
Share on other sites

Hi!

I just downloaded from D2D and patched successfully. I get the same FP error as Milamber when I start a fresh new game but I use no AMD proc.

Instead an Intel Pentium® D 3.0GHZ.

File version of UCAWA modified Apr 13 2006 1:14 AM

Thanks in advance

Martin

Share this post


Link to post
Share on other sites

A Duron 1.3 Ghz is way below the minimum system requirements for the game (the minimum is a Pentium 4 2.0Ghz or equivalent AMD processor (i.e. Athlon XP 2000+ at the very least)

UCAWA product info

my UCAWA was created 11 August 2005, 07:01:00

and modified 13 April 2006, 08:13:59

my UCAWAMP was created 11 August 2005, 07:01:00

and modified 13 April 2006, 08:12:01

so something went wrong with your patching process.

Share this post


Link to post
Share on other sites

Oy, then I have wasted everyone's time due to my overlooking the obvious. My apologies.

I shall now retire to my side of the keyboard with my thanks for your patience...

Share this post


Link to post
Share on other sites

quote:


Originally posted by TroKhon:

Hi!

I just downloaded from D2D and patched successfully. I get the same FP error as Milamber when I start a fresh new game but I use no AMD proc.

Instead an Intel Pentium® D 3.0GHZ.

File version of UCAWA modified Apr 13 2006 1:14 AM

Thanks in advance

Martin


Then something is wrong on your end because this issue ONLY affects AMD processors.

And please fix your sig and also enter the version numbers for your drivers, or your profile - and posts - will be deleted.

Share this post


Link to post
Share on other sites

quote:


Originally posted by Matchoo:

Both singleplayer and multiplayer are running great for me now.

Thanks.


Please complete your profile.

Share this post


Link to post
Share on other sites

quote:

Originally posted by Supreme Cmdr:

quote:

Originally posted by Matchoo:

Both singleplayer and multiplayer are running great for me now.

Thanks.

Please complete your profile.


Done

Share this post


Link to post
Share on other sites

I hope my Sig fits right in now.

Any suggestions what i can do now?

Shall I reinstall the whole game from scratch

I don't know if I can do this without any license trouble.

Thanks Martin

Share this post


Link to post
Share on other sites

Hi again.

What I tried now was the following.

I changed version info in settings.ini back to version=1.00.09

and patched with 1.10 D2D.exe

Game runs fine.

I tried up to 1.13 no problem

after patching to 1.14 I feel sorry but i get

Runtime Error!

R6002

- floating point not loaded

I checked twice!

Share this post


Link to post
Share on other sites

First of all, this [compiler] bug does not affect Intel CPUs. So I have no idea what you're doing or why you're getting that. I'm stumped.

HOW are you patching this? Are you using the game Updater or downloading the patch from the D2D patch page? If you are downloading it directly from the D2D patches page. Don't. It has not yet been updated by them.

Also....

What is the date/time/size stamp of the ucAWA_1.00.14_D2D.exe file that is downloaded (by the game Updater) and copied to your game folder prior to patching? After the patch is completed, go to the game folder and locate this file.

What is the date/time/size stamp of the UCAWA.EXE and UCAWAMP.EXE files created by the patch?

btw You can open Explorer and right-click on the file and go into properties to get this info.

Anyway, until we figure out wtf is going on, roll back to 1.00.13. Just set your INI to 1.00.12 and run the Updater.

Share this post


Link to post
Share on other sites

Hi!

Thanks f├╝r your fast and helpfull response (as allways )

I have been allways trying the Game Updater!

My files show the following dates

UCAWA.EXE : 13. April 2006, 01:14:00

UCAWAMP.EXE : 13. April 2006, 01:14:00

ucAWA_1.00.14_D2D.exe : created 16. April 2006, 11:25:45

changed: 16. April 2006, 11:27:19

Rolled back to 1.00.13 which works fine for me!

Thanks Martin

PS. Tell me if anything else can be done by me to help you figure this out.

Share this post


Link to post
Share on other sites

I asked for the sizes of those two EXE files.

Also, please delete that ucAWA_1.00.14_D2D.exe file and run the Updater again to go to 1.00.14. Then run the game again and get back to me please.

Share this post


Link to post
Share on other sites

Hi!

Sorry for the missing sizes

UCAWA.EXE : 13. April 2006, 01:14:00

2,52 MB (2.648.065 Bytes)

UCAWAMP.EXE : 13. April 2006, 01:14:00

2,72 MB (2.859.521 Bytes)

ucAWA_1.00.14_D2D.exe :

created 16. April 2006, 20:04:26

changes 16. April 2006, 20:05:57

size 19,6 MB (20.567.318 Bytes)

did a delete of the ucAWA_1.00.14.D2D.exe and an update via updater.

Unfortunately problem persists.

Thanks Martin

Share this post


Link to post
Share on other sites

OK, this is weird on so many levels, its not even funny.

Please rollback to 1.00.13 for now. Tomorrow I'll look into this some more and try to figure out wtf is going on here.

btw, do you get this error in both single and multiplayer? Also, at one point do you get the error?

Share this post


Link to post
Share on other sites

btw, you are certain that you have an Intel CPU or did you upgrade and forgot to update your profile?

Share this post


Link to post
Share on other sites

quote:


Originally posted by Milamber:

Oy, then I have wasted everyone's time due to my overlooking the obvious. My apologies.

I shall now retire to my side of the keyboard with my thanks for your patience...


Well, you can always roll back to 1.00.13 if that works for you.

Share this post


Link to post
Share on other sites

quote:


Originally posted by TroKhon:

absolutely certain Its an Intel Dual Core

bought this one extra for its power


OK, lets go to plan C

  1. Rename your [1.00.13] UCAWA.EXE and UCAWAMP.EXE files to .BAK
  2. Download this D2D file and extract into your game folder
  3. Run both the sp & mp versions of the game and let me know if either works or not.

If this version still does not work, just revert back to 1.00.13 by deleting the files and restoring the backup versions in step #1

Also, I'd like anyone with the D2D version to try this as well please.

Share this post


Link to post
Share on other sites

Hi!

I did exactly what you wrote above.

Unfortunately both exe's do not start the game at all. I have absolutely no idea why. There is also no message at all. Mouse shows for about a quarter of a second a busy cursor and that is all thats happening.

File information:

ucAWA.exe

created 18. April 2006, 18:35:55

changed 18. April 2006, 11:33:52

2,52 MB (2.648.577 Bytes)

and

ucAWAmp.exe

created 18. April 2006, 18:43:40

changed 18. April 2006, 11:36:42

2,72 MB (2.860.033 Bytes)

Martin

Share this post


Link to post
Share on other sites

Hi!

Due to the directX upgrade the application starts now, but before the main menu appears directly after the intro animation the application stops with the following error.

Runtime error!

The application has requested the Runtime to terminate it in an unusual way.

this happens for the SP and MP version.

Martin

Share this post


Link to post
Share on other sites

OK, back to the drawing board. I'll get back to you tomorrow with another test.

This is just the usual bullshit from Microsoft.

In the meantime, Matchoo, can you try this version as well please and let me know your results?

Share this post


Link to post
Share on other sites
Sign in to follow this  

×