Warzone 2100 Forums

b)whats up with this unit limit? I like to build series of towers, but if i do so, i am only allowed to have 14 tanks (when NPC have many). It would be great to be able to toggle unit limitations.

WTF? I think there's no unit limit...

I think they're referring to the 15 truck/constructor limit.
In the campaign, there seems to be a limit of ~100 mobile units, but I'm not sure how that relates to skirmish/MP.

Keith

avuthless wrote:a) My PC is up to date and quite new so game runs great, but sometimes (when i play for more than 2hrs) game just closes. I saw that this happens to people sometimes. (Played twice today, first time crash at 2:14 hrs of play, second flawless 5hrs play).

This usually happens when you have an old computer. Update your drivers; if it still occurs: buy a newer computer. If you can't, well... save often.

Of course, it's also entirely possible you've hit upon a crash bug. Can you upload a crash report? (In Windows, it's warzone2100.RPT)

avuthless wrote:b)whats up with this unit limit? I like to build series of towers, but if i do so, i am only allowed to have 14 tanks (when NPC have many). It would be great to be able to toggle unit limitations.

The unit limit is currently 15 constructors and 150 total units. It has not changed in this beta. Individual version threads are usually for posting feedback to the specific version being released. Unless it is something specific to 2.3 beta 11a, I encourage to post your feedback elsewhere (such as in the Project Feedback forums).

avuthless wrote:c)i played with my friends and 4 maxed NPCs in map "The Pit" with no teams set. First i saw NPCs with nice armies and quite many units, but in the end, he had like 20 cyborgs and he did nothing. He was just keeping them in his base and rebuilding any of them missing. It was very easy to kill him in the end. Like someone wrote before me "they run out of units".

The default AI can do weird things like that. Try the bundled "DyDo AI" - it can be better at things like that.

avuthless wrote:d)Thats a random thing. Did you try to pick a barrel of energy with a sensor tank? All artillery starts firing that barrel. This happens if you try to pick up artifacts too. It seems the sensor tank transmits those coordinates as a target. Nothing much, but may be annoying for some.

I have heard about this bug before, but have not been able to reproduce it. When I try to pick up an oil barrel or artifact with a sensor tank, the sensor tank goes over to it and picks it up.

Can you be more specific about the situation in which your sensor started firing on the barrel/artifact?

Saberuneko wrote:Yes, it happens to me with the b11a.

Works fine on this end...

Anyone else?

Weirdly, with my new win7 that cursor doesn't get stuck...

But...

I've noticed several additional sync problems in MP, (like dead players that are alive for others, or units appearing or vanishing without any apparent reason)

What can I send you for tracking these problems? (It was an 8P game)

Is there a ETA on the next release?
I saw the changelog was updated for a release but I can't find any release anyplace?

Saberuneko wrote:I've noticed several additional sync problems in MP, (like dead players that are alive for others

I have seen this a few times but cannot find anything in Trac. What the host will say is he experienced extreme lag and warzone stop responding for a short time. A player will disconnect but only the host will see that. The game will end for the host but the other players still see the disconnected player as being in game and will have to kill the disconnected player to get the win. I have not seen this as host though but have experienced the extreme lag problem a few times when pings were excellent.

BunkerBlaster wrote:

Saberuneko wrote:I've noticed several additional sync problems in MP, (like dead players that are alive for others

I have seen this a few times but cannot find anything in Trac. What the host will say is he experienced extreme lag and warzone stop responding for a short time. A player will disconnect but only the host will see that. The game will end for the host but the other players still see the disconnected player as being in game and will have to kill the disconnected player to get the win. I have not seen this as host though but have experienced the extreme lag problem a few times when pings were excellent.

You described my problem with 100% exactitude.

Saberuneko wrote:I've noticed several additional sync problems in MP, (like dead players that are alive for others

BunkerBlaster wrote:What the host will say is he experienced extreme lag and warzone stop responding for a short time.

Saberuneko wrote:You described my problem with 100% exactitude.

I have searched but your the only one that has mentioned this and I am surprised because I've seen many in game talk about it. The only thing I left out is warzone does not allways write to the log files when this happens. I have one log saved from a 3 min freeze but all players were disconnected.
[connectionIsOpen] Read queue empty - failing (ECONNRESET).

I would love to submit a ticket but dont have one were others saw dead players. I have removed all Tsr's from my comp and will play a few games this weekend to see if it repeats.

Ticket 1270 might be related http://developer.wz2100.net/ticket/1270
Also ping is somewhat irrelevant viewtopic.php?f=30&t=5041

Zarel wrote: Can you be more specific about the situation in which your sensor started firing on the barrel/artifact

This I believe will also happen in campaign and here is how it happens.....
1)Build a sensor unit
2)Find a barrel, artifact, or something else you can pick up
**Make sure you have some kind of artillery in range, ripple rockets, howitzers, Arch Angel, etc. for this next step
3)With your sensor unit selected click directly on the item to pick up
4)It will automatically be targeted by all your artillery in range
5)Watch as shells and/or rockets hit the item.

That is how it happens, hope it happens to you so this can be solved, because it messes with the priority of targets if they were firing at a unit.

avuthless wrote:a) My PC is up to date and quite new so game runs great, but sometimes (when i play for more than 2hrs) game just closes. I saw that this happens to people sometimes. (Played twice today, first time crash at 2:14 hrs of play, second flawless 5hrs play).

Zarel wrote:Update your drivers; if it still occurs: buy a newer computer.

My Pc is up to date and quite new also. About 6 months old. Buying a new computer did not fix warzone (at least not for me). Not the latest and greated but it is a newer computer. Avuthless said game just closes then he calls it a crash. To me its two different things not that my analogy is correct. I call a crash when the operating system creates event messages and crash dumps. The game just closing without actually creating any operating system events or crash dumps is well just closing. The game just closing or exiting on its own not only happens with b11a but was also a problem with the original game. I use to think I click the mouse to fast or I press the wrong key. Many of us had this problem back when we played on mplayer and found that rebooting the machine before playing would solve the problem. For me game just exiting has occured on Windows 95, Windows 98, Windows XP sp1, sp2, sp3. I did not run windows 7 long enough to find out. Anything from a 333 mhz comp with little memory and crappy graphics card to a 2.8 Ghz intel 32 bit duo core Radeon 9600 Graphics card or AMD 2.7 Ghz 64 bit duo core with 2 gig memory and Nvidia graphics. For Windows the minumim requirements for the game is now Windows 2000.
avuthless 2nd game was longer because he most likely rebooted. As far as advice the only thing I would add is dont have programs that you dont need load at startup and reboot your machine before playing a long game.
You may also want to read this viewtopic.php?f=32&t=4053
Possibly related http://developer.wz2100.net/ticket/1713

BunkerBlaster wrote:My Pc is up to date and quite new also. About 6 months old. Buying a new computer did not fix warzone (at least not for me). Not the latest and greated but it is a newer computer. Avuthless said game just closes then he calls it a crash. To me its two different things not that my analogy is correct. I call a crash when the operating system creates event messages and crash dumps. The game just closing without actually creating any operating system events or crash dumps is well just closing. The game just closing or exiting on its own not only happens with b11a but was also a problem with the original game. I use to think I click the mouse to fast or I press the wrong key. Many of us had this problem back when we played on mplayer and found that rebooting the machine before playing would solve the problem. For me game just exiting has occured on Windows 95, Windows 98, Windows XP sp1, sp2, sp3. I did not run windows 7 long enough to find out. Anything from a 333 mhz comp with little memory and crappy graphics card to a 2.8 Ghz intel 32 bit duo core Radeon 9600 Graphics card or AMD 2.7 Ghz 64 bit duo core with 2 gig memory and Nvidia graphics. For Windows the minumim requirements for the game is now Windows 2000.
avuthless 2nd game was longer because he most likely rebooted. As far as advice the only thing I would add is dont have programs that you dont need load at startup and reboot your machine before playing a long game.
You may also want to read this viewtopic.php?f=32&t=4053
Possibly related http://developer.wz2100.net/ticket/1713

A new machine doesn't mean it will automatically work.
The main problem from what I am reading is that if the openGL drivers aren't up to the job, then they tend to end the game with no user warning.
You should never have to reboot your machine just to play a game, if that is the case, then there is some serious issues with your machine.

BunkerBlaster wrote:Possibly related http://developer.wz2100.net/ticket/1713

Flank4 wrote:A new machine doesn't mean it will automatically work.
The main problem from what I am reading is that if the openGL drivers aren't up to the job, then they tend to end the game with no user warning.

Should I delete the Ticket I submitted or do you want to close it? Im sorry I did not think it was the drivers. At one time I did get errors specificly referencing the drivers and it was in every Warzone log. I tried new and old from Nvidia but ended up going with the version approved by microsoft and the Warzone log stop complaining about drivers. Which I now read is what not to do per next quote.

Buginator wrote:Use different openGL drivers. Try older / newer / beta, and get them directly from Nvidia.com

Zarel wrote:Well, I've added "install the latest drivers" to the system requirements page. Do you think that's enough?

The ticket I submitted rarely happens, maybe 1 time a month and I dont see were its saying anything about drivers like it did months ago. I thought it was just listing the version for reference. I have a few other openGL games and they have no problem. I noticed the Nvidia driver for the mac has a specific link for it. Would be really nice if the same could be done for windows so Im not spinning my wheels. I will reinstall the most recent from Nvidia again.

Flank4 wrote:You should never have to reboot
your machine just to play a game, if that is the case, then there is some
serious issues with your machine..

Didn't "have to reboot". Just noticed game would last a long time without exiting if the machine had a clean boot. Im only trying to help by being as specific as I can. Perhaps I should have not referenced the original game. With beta 11a I tested it on my machine with the same drivers as the ticket I submitted and played in skirmish by building a bunch of arty and defence then leaving the game run overnight. The game lasted over 12 hours and never closed and no errors in log. As far as the reboot I only do it for Warzone. Im a little old school thinking back when software had black lists (software that was not compatable with others). Some incompatability still exists (not on my machine) and would be happy to discuss that if you want to make a thread for it in the right place.

BunkerBlaster wrote: Should I delete the Ticket I submitted or do you want to close it? Im sorry I did not think it was the drivers. At one time I did get errors specificly referencing the drivers and it was in every Warzone log. I tried new and old from Nvidia but ended up going with the version approved by microsoft and the Warzone log stop complaining about drivers. Which I now read is what not to do per next quote.

I am betting one of the devs will eventually look at it. They all seem to have taken a vacation from warzone.

Didn't "have to reboot". Just noticed game would last a long time without exiting if the machine had a clean boot. Im only trying to help by being as specific as I can. Perhaps I should have not referenced the original game. With beta 11a I tested it on my machine with the same drivers as the ticket I submitted and played in skirmish by building a bunch of arty and defence then leaving the game run overnight. The game lasted over 12 hours and never closed and no errors in log. As far as the reboot I only do it for Warzone. Im a little old school thinking back when software had black lists (software that was not compatable with others). Some incompatability still exists (not on my machine) and would be happy to discuss that if you want to make a thread for it in the right place.

I don't know of a good place for a thread for this, but, the main reason you don't have to reboot anymore is because XP & Vista & Win7 are much better than windows 95&98 ever was. Much better kernel.

Flank4 wrote:I am betting one of the devs will eventually look at it.

I haven't closed the ticket since the crashdump isn't clearly a driver problem.