Warzone 2100 3.2.3 crashed

Do you need help? Ask here!

Bug reporting belongs here: http://developer.wz2100.net/newticket
Post Reply
Isolatid
New user
Posts: 2
Joined: 22 Sep 2018, 19:34

Warzone 2100 3.2.3 crashed

Post by Isolatid » 23 Sep 2018, 17:04

Hey people.

Sorry for my english im french, i have a problem with the last version of warzone. i don't know why.

maybe this can help :


--- Starting log [C:\Users\Isolatid\Documents\Warzone 2100 3.2\logs\WZlog-0923_164529.txt]---
info |04:45:29: [realmain:938] Using C:\Users\Isolatid\Documents\Warzone 2100 3.2\logs\WZlog-0923_164529.txt debug file
info |04:45:41: [pal_Init:51] Buffer overrun reading palette data
info |04:45:41: [pal_Init:51] Assert in Warzone: piepalette.cpp:51 (lenLeft >= 0), last script event: ''
info |04:45:41: [pal_Init:51] Buffer overrun reading palette data
info |04:45:41: [pal_Init:51] Assert in Warzone: piepalette.cpp:51 (lenLeft >= 0), last script event: ''
info |04:45:41: [pal_Init:51] Buffer overrun reading palette data
info |04:45:41: [pal_Init:51] Assert in Warzone: piepalette.cpp:51 (lenLeft >= 0), last script event: ''
info |04:45:41: [pal_Init:51] Buffer overrun reading palette data
info |04:45:41: [pal_Init:51] Assert in Warzone: piepalette.cpp:51 (lenLeft >= 0), last script event: ''
info |04:45:41: [pal_Init:51] Buffer overrun reading palette data
info |04:45:41: [pal_Init:51] Assert in Warzone: piepalette.cpp:51 (lenLeft >= 0), last script event: ''
info |04:45:41: [pal_Init:51] Buffer overrun reading palette data
info |04:45:41: [pal_Init:51] Assert in Warzone: piepalette.cpp:51 (lenLeft >= 0), last script event: ''
info |04:45:41: [pal_Init:51] Buffer overrun reading palette data
info |04:45:41: [pal_Init:51] Assert in Warzone: piepalette.cpp:51 (lenLeft >= 0), last script event: ''
info |04:45:41: [pal_Init:51] Buffer overrun reading palette data
info |04:45:41: [pal_Init:51] Assert in Warzone: piepalette.cpp:51 (lenLeft >= 0), last script event: ''
error |04:45:47: [khr_callback:139] GL::API(Performance:Medium) : Pixel-path performance warning: Pixel transfer is synchronized with 3D rendering.



Thanks

User avatar
NoQ
Special
Special
Posts: 6200
Joined: 24 Dec 2009, 11:35
Location: /var/zone

Re: Warzone 2100 3.2.3 crashed

Post by NoQ » 24 Sep 2018, 02:17

Looks like a broken mod, are you using mods?

Isolatid
New user
Posts: 2
Joined: 22 Sep 2018, 19:34

Re: Warzone 2100 3.2.3 crashed

Post by Isolatid » 24 Sep 2018, 13:03

i don't know, i just downloaed the last version and tried to play directly :)

User avatar
NoQ
Special
Special
Posts: 6200
Joined: 24 Dec 2009, 11:35
Location: /var/zone

Re: Warzone 2100 3.2.3 crashed

Post by NoQ » 26 Sep 2018, 04:43

Weird. Could you attach a crash dump? Still, see if deleting (or moving away) mods and maps helps.

User avatar
Morgana
Trained
Trained
Posts: 72
Joined: 24 Feb 2016, 22:04

Re: Warzone 2100 3.2.3 crashed

Post by Morgana » 30 Oct 2018, 10:24

(error |04:45:47: [khr_callback:139] GL::API(Performance:Medium) : Pixel-path performance warning: Pixel transfer is synchronized with 3D rendering.)
have you one offboard graphic card 3D ?
the problem is not mods, the maps yes.

1. you have the maps folder, maps the warzon 2100 2.8.x the game can error to get. warzone 2100 3.1.x maps is gray zone.
2. or the version is old Shader/OpenGL/OpenCLT i have Vulkan, or the microsoft DirectX is old.
3. you have the warzone 2100 3.2.3 install of the old ver. ?
4. the game warzone 2100 3.2.3 ist not correctly install the 1% missing
5. game download and is not correctly download the 50kbs missing and can install and play error
6. CPU GHz can the game not more open.
7. ok send the floder mods Desktop and delete all the mods, not the floder.
8. the game missing the .exe or base or mp or or or...
I paint the images :geek:
for 3.1.5 -> 3.2.3 -> master :lecture:

User avatar
andrvaut
Trained
Trained
Posts: 117
Joined: 02 Jan 2016, 12:44

Re: Warzone 2100 3.2.3 crashed

Post by andrvaut » 30 Oct 2018, 13:08

vaut ΣΑ [GN], ru streamer.
Tournaments channel: https://www.youtube.com/channel/UCzusNa-54ydodtSz2TdHFww

Post Reply