[HELP] this happened in ver. 2.1 and now happened ver. 2.2
Re: [HELP] this happened in ver. 2.1 and now happened ver. 2.2
You did the backtrace when Warzone was frozen (cuando Warzone está frizado), right?
Re: [HELP] this happened in ver. 2.1 and now happened ver. 2.2
RightZarel wrote:You did the backtrace when Warzone was frozen (cuando Warzone está frizado), right?
Re: [HELP] this happened in ver. 2.1 and now happened ver. 2.2
The 4c-cliffBeta.wz works .Each times.Zarel wrote:Can you give a screenshot of your problems with cliffBeta?
Acts differently each time. depends if you play with 1, 2 or 3 opponents.
Playing with 4 teams it's more stable and less failure.
I'm playing in several ways. Tell me if this way it's OK.
I will send you a little detail as far as I play.
First option
Team B ..... out Black terrain.works Ok Although not visualize the area to build with white or green rectangle. but builds
Last edited by topo1948 on 06 Oct 2009, 09:17, edited 1 time in total.
Re: [HELP] this happened in ver. 2.1 and now happened ver. 2.2
Zarel 4c-cliffBeta.wz
Team C ....... out
Once you get the left border screen moving the mouse, the hole terrain became black. anyway still working.
moving back to the right side and get Ok.
now it's different. On previus case ( Team A .....out ) the black terrain it was there from the stars.
As I believe that everything can serve, I will not fail to mention that this happened 4 times exactly the same.
Even worse. Once the progam went off by pressing the square with the options you accept.
Now i'll try Team B and C ...... out.
Team C ....... out
Once you get the left border screen moving the mouse, the hole terrain became black. anyway still working.
moving back to the right side and get Ok.
now it's different. On previus case ( Team A .....out ) the black terrain it was there from the stars.
As I believe that everything can serve, I will not fail to mention that this happened 4 times exactly the same.
Even worse. Once the progam went off by pressing the square with the options you accept.
Now i'll try Team B and C ...... out.
Re: [HELP] this happened in ver. 2.1 and now happened ver. 2.2
Zarel 4c-cliffBeta.wz
Team B and C ...... out.
Start fine the black terrain section That's not all. is a mixture of the problems appeared in the previous two.
As it accepts 3 attach. let me find a way to explain better.
Team B and C ...... out.
Start fine the black terrain section That's not all. is a mixture of the problems appeared in the previous two.
As it accepts 3 attach. let me find a way to explain better.
Re: [HELP] this happened in ver. 2.1 and now happened ver. 2.2
I fixed the cliffBeta problem two days ago or so. Will appear in forthcoming 2.2.4 release. It only happens on certain maps.
Re: [HELP] this happened in ver. 2.1 and now happened ver. 2.2
Something similar whith Sk-Pass-Assault
I'm using version 2.2.1.
Just in case, this accept me use new maps.
with Sk-proisles-T1
This map once you click on, shoot down the game.I'm using version 2.2.1.
Just in case, this accept me use new maps.
Re: [HELP] this happened in ver. 2.1 and now happened ver. 2.2
They said they fixed it in 2.2.4topo1948 wrote:Something similar whith Sk-Pass-Assault
I'm using version 2.2.1.
Just in case, this accept me use new maps.
Per wrote:I fixed the cliffBeta problem two days ago or so. Will appear in forthcoming 2.2.4 release. It only happens on certain maps.
This is a waste of space. Something important should be here.
Re: [HELP] this happened in ver. 2.1 and now happened ver. 2.2
Okay.
It's Buggy's sound patch: http://developer.wz2100.net/ticket/770
That's what broke Warzone for you. Let's see if it can be fixed.
Also possibly see this list of the changes between 2.2.1 and 2.2.2:
http://developer.wz2100.net/log/branche ... &limit=100
The freeze was in sound code, which makes me suspect Buggy's sound patch.
It's Buggy's sound patch: http://developer.wz2100.net/ticket/770
That's what broke Warzone for you. Let's see if it can be fixed.
Also possibly see this list of the changes between 2.2.1 and 2.2.2:
http://developer.wz2100.net/log/branche ... &limit=100
The freeze was in sound code, which makes me suspect Buggy's sound patch.
Re: [HELP] this happened in ver. 2.1 and now happened ver. 2.2
Zarel wrote:Okay.
It's Buggy's sound patch: http://developer.wz2100.net/ticket/770
That's what broke Warzone for you. Let's see if it can be fixed.
Also possibly see this list of the changes between 2.2.1 and 2.2.2:
http://developer.wz2100.net/log/branche ... &limit=100
The freeze was in sound code, which makes me suspect Buggy's sound patch.
![Eh? O_o](./images/smilies/icon_eh2.gif)
I think that is a red herring.
He should edit the config file and turn music off.
Code: Select all
music_enabled=0
cdvol=0
topo1948, what version of vorbis do you have?
and it ends here.
Re: [HELP] this happened in ver. 2.1 and now happened ver. 2.2
o_O It was a change in 2.2.1 -> 2.2.2 that caused the problem. The freeze is in sound code.Buginator wrote:How do you figure this? Did you bother to look at the sound patch? I really doubt that checking to see if a sample is in range will result in this.
I think that is a red herring.
He should edit the config file and turn music off.You should also give him a non-debug build of 2.2.3 so he can try.Code: Select all
music_enabled=0 cdvol=0
topo1948, what version of vorbis do you have?
What other evidence are you looking for?
Disabling sound is a workaround, not a solution.
Re: [HELP] this happened in ver. 2.1 and now happened ver. 2.2
I didn't say disable sound, I said disable music.Zarel wrote: o_O It was a change in 2.2.1 -> 2.2.2 that caused the problem. The freeze is in sound code.
What other evidence are you looking for?
Disabling sound is a workaround, not a solution.
Code: Select all
#6 0x0015bde8 in sound_DecodeOggVorbis ()
#7 0x000386f8 in sound_PlayStreamWithBuf ()
#8 0x000374cc in cdAudio_OpenTrack ()
#9 0x000376f8 in cdAudio_TrackFinished ()
and it ends here.
Re: [HELP] this happened in ver. 2.1 and now happened ver. 2.2
Music isn't sound? o_O I think I understand what you're trying to say, but I'm not sure. We have a different engine for music than for other sounds?
Re: [HELP] this happened in ver. 2.1 and now happened ver. 2.2
Heh. well, it is sound, but we can turn music off, and still have the sound effects.Zarel wrote:Music isn't sound? o_O I think I understand what you're trying to say, but I'm not sure. We have a different engine for music than for other sounds?
And the routines for music are different than what we use for in-game sounds.
and it ends here.