 Show Posts
|
|
Pages: 1 2 [3] 4 5
|
|
51
|
Awesomeware / AwesomeMod! / Re: AwesomeMod Updater (v2.4 - Updated 01/07/2010)
|
on: 2011 January 23, 09:49:50
|
The updater bat is giving me an error code 9, read the readme;
<snip>
I check, 3booter is in the Late Night directory. I'm going to try and reinstall/redownload the updater manually, see what it gives me. 3booter worked on it's own.
Error 9 means something else: Error code 9
Meaning: The updater couldn't check for compatibility with your game version. This is probably because the server is down.
How to solve: Try again later or check your internet connection. Do you have an old readme file? To all: It turns out that I was 'abusing' the file host. They removed all files and pages, so the updater can't check for newer versions or download compatibility.txt to check for patch compatibility. I am now working on v2.4.1, which will remove all update checks and other things which involve that file host. I'll have to find a new one, which doesn't remove everything for... uh, semi-abuse. Update coming soon. EDIT: It's there. EDIT2: Patch compatibility check and test version download wil return in v2.5. Auto-update option will change to a notification. Updated to v2.4.1 (v2.4.1.110) |
|
|
|
|
54
|
Awesomeware / AwesomeMod! / Re: AwesomeMod Updater (v2.4 - Updated 01/07/2010)
|
on: 2011 January 11, 05:47:02
|
Problem - I use the aweconfig.package and placed it in the AwesomeMod Updater folder - but the way you have it configured now, the package is being deleted - can you configure it Not to delete this package?
The updater should not delete aweconf.package. I didn't configure it like that, and aweconf isn't mentioned in the whole file. It only replaces awesome.package and does nothing else with the files in there. I use the aweconfig myself, and it works fine. Anyone else having this problem? |
|
|
|
|
55
|
Awesomeware / AwesomeMod! / Re: What do those "chimes" mean?
|
on: 2011 January 09, 17:24:55
|
Yo, FlamingoKicker. Stop creating new threads for random issues! There is a bug report thread, you know. Also, this is an already-known issue. Search moar! What is MOAR?  Lurk moar! |
|
|
|
|
57
|
Awesomeware / AwesomeMod! / Re: AwesomeMod Updater (v2.3/v2.4beta - Updated 12/30/2010)
|
on: 2011 January 03, 15:38:30
|
You clearly don't know what you are talking about, do you? This updater is NOT AwesomeMod. All version numbers, bug reports and feature lists in this thread apply to this updater and NOT AwesomeMod. There is NO test version of AwesomeMod available, as you should have discovered by SEARCHING. EDIT: I saw what you did there. |
|
|
|
|
58
|
Awesomeware / AwesomeMod! / Re: AwesomeMod Translation Thread
|
on: 2011 January 02, 13:31:42
|
A request again to make more strings translateable. I agree that deep-level debugging strings don't need translation, but in my opinion the output of various frequently used commands (fixall, purgegenetichair, destroyallhumans, etc.) should be translateable. Also, when hovering over a derelict vehicle map tag, the whole tooltip is translated, but "No driver!" is not. And, finally, these strings, but I guess those are controlled by the game, and not AwesomeMod. |
|
|
|
|
60
|
Awesomeware / AwesomeMod! / Re: AwesomeMod Updater (v2.3/v2.4beta - Updated 12/30/2010)
|
on: 2010 December 30, 14:34:37
|
|
v2.4beta
If I don't get any feedback or bug reports for one week or so, this version will replace v2.3.
New in v2.4:
- Fixed issues with Windows XP;
- Reduced file size of updater.bat by 42%;
- New file host makes the process 91% faster;
- Improved wget and unzip check;
- Fixed check for test version;
- Other minor changes. See Changelog for details.
So, please test this and give feedback.
v2.4beta - build 14 (v2.4.0.103) v2.4.0.107 is attached below. If I fix something in the next build, the updater will download it.
December 31: Updated to build 15 (v2.4.0.104). Build 14 will download it automatically.
January 2: Updated to build 16 (v2.4.0.105). Build 14 and 15 will download it automatically.
January 4: Updated to v2.4.0.106 (beta). Build 14, 15 and 16 will download it automatically.
January 4: Updated to v2.4.0.107 (beta). This build should fix imcompatibilities with Windows XP.
January 7: Updated to v2.4.0.108 (final).
January 7: Updated to v2.4.0.109 (final).
Attachment deleted. Final version available in original post.
|
|
|
|
|
61
|
Awesomeware / AwesomeMod! / Re: AwesomeMod Updater (v2.3 - Updated 12/15/2010)
|
on: 2010 December 15, 17:12:50
|
|
Updated to v2.3 (v2.3.0.89)
Beta builds (60, 61, 62) should download this update automatically.
- New file, locale.aweupd: this file should be placed in the Windows directory (along with wget.exe and unzip.exe);
- Added ability to update itself;
- Built-in AM test version download support. No need for separate awetest versions anymore;
- Other minor changes. See Changelog for details.
|
|
|
|
|
63
|
Awesomeware / AwesomeMod! / Re: AwesomeMod Updater (v2.2.4/v2.3beta - Updated 12/7/2010)
|
on: 2010 December 13, 07:56:40
|
I tried the newest version, if just to see if it no longer gives me an Error 1, but, unfortunately, it still does. The new file is in the windows directory and everything.
I'm... not even sure why I'm still getting this error, but eh, 64x systems just always seem to have weird stuff happening all around.
Build 61 hopefully fixes this. Unfortunately, build 60 checks for error 1 before checking for an update, so you'll have to download build 61 manually. Note, error 1 is an error which shouldn't occur on any computer, so there might be something wrong with your pc. Other users of build 60 will be notified of the update. This is a nice check if that works, too. Expected behaviour: screen with "Build 61 has been downloaded", pressing 1 will update it and then immediately start the new build. Pressing 2 will not update it and continue with build 60. Pressing 3 will exit immediately. Does this work? Hyper late edit: removed not-working link to build 61. |
|
|
|
|
64
|
Awesomeware / AwesomeMod! / Re: AwesomeMod Updater (v2.2.4/v2.3beta - Updated 12/7/2010)
|
on: 2010 December 07, 15:28:42
|
|
v2.3beta
At this point, I would consider v2.3 stable enough to replace v2.2.4. But, because of the issues with v2.2 after the release, I offer it as a beta version first. If I don't get any feedback or bug reports for one week or so, it will replace v2.2.4.
New in v2.3:
- The updater can now update itself. However, it will ask you if you want to apply the update or not.
- New way of finding the Documents\Electronic Arts\The Sims 3 folder: the updater finds the locale code (like en-US) in the registry and compares it with the new inculded file, locale.aweupd, which needs to be placed in the Windows directory.
- Built-in AwesomeMod test version download: downloading a seperate awetest version isn't required anymore.
- Other minor inprovements; see the Changelog for details.
So, please test this and give feedback.
v2.3beta - build 60 is included below. If I fix something in the next build, the updater will download it.
December 13: Updated to build 61. Build 60 will download it automatically.
December 14: Updated to build 62. Build 60 and 61 will download it automatically.
December 15: Updated to build 63 (final). Build 60, 61 and 62 will download it automatically.
Attachment deleted. Final version available in original post.
|
|
|
|
|
66
|
Awesomeware / AwesomeMod! / Re: AwesomeMod Updater (v2.2.2 - Updated 11/25/2010)
|
on: 2010 November 25, 20:24:34
|
The updater works just fine now, though a new problem has risen that's never come up before. Usually, I use program in conjunction with Granthes's Custom Launcher (which now has included a way to use a custom startup file if needed).
Now, when I use the updater with the Custom Launcher, I get an error code 1. When I use the updater or the custom launcher by itself, however, they both work just fine. This has never come up before, so I figured I'd report it in case other people have the same problem, or if it was a symptom of a larger problem.
If you were already aware of this, my apologies. I haven't had any problem using both until v.2.2.1.
Error code 1 would indicate that there is both a 32-bit AND a 64-bit registry entry of The Sims 3 in your registry, which is practically impossible. However, v2.2.2 ignores this error and just continues. ETA: I tried that Custom Launcher thing in combination with v2.2.1 and it worked just fine, though.
Updated to v2.2.2- Ignores error 1. Updating to v2.2.2 is not necessary if you didn't have issues with v2.2.1. |
|
|
|
|
74
|
Awesomeware / AwesomeMod! / Re: AwesomeMod Updater Revived (v1.8.1/v2.1 - Updated 10/31/2010)
|
on: 2010 October 31, 17:12:53
|
Really? before i start it claims i have mods that dont work with my version. if i start anyway, it gets all the way to the end of the load screen, and it CTD. can you direct me to a way to fix it? i have the latest AM and if i delete it i can get through no problem.
Yeah, I know. You've already posted this in the Bug Report Thread. Look there. |
|
|
|
|
|
