MantisBT - Zandronum
View Issue Details
0002098Zandronum[All Projects] Bugpublic2015-02-10 21:012015-02-25 12:58
Fused 
 
highmajoralways
closedno change required 
MicrosoftWindows8
2.0-beta 
2.0 
0002098: Latest build causes slope and height malfunctions in Zombie Horde.
As found while testing, on map ze15 most of the map will bug and cause sectors to change height and perhaps even slope.
Build:'http://s1.plusreed.com/jenkins/zandronum/zandronum-150209-1709_265.zip [^]'

load with:

skulltag actors/data
zh-beta27.pk3'http://www.best-ever.org/download?file=zh-beta27.pk3 [^]'
zh-beta27-fix3.wad (optional)'http://www.best-ever.org/download?file=zh-beta27-fix3.wad [^]'
zh-mappack10.pk3'http://www.best-ever.org/download?file=zh-mappack10.pk3 [^]'
zh-testpack_r25.pk3'http://www.best-ever.org/download?file=zh-testpack_r25.pk3 [^]'
zh-testpack_F01.pk3'http://www.best-ever.org/download?file=zh-testpack_f01.pk3 [^]'

changemap on ze15. Bug should be immediatley visible

1.3:'http://prntscr.com/63imuw [^]'
2.0:'http://prntscr.com/63immo [^]'
___________
1.3:'http://prntscr.com/63ina0 [^]'
2.0:'http://prntscr.com/63ini9 [^]'
No tags attached.
related to 0002114closed Edward-san Latest build causes skybox hom in Zombie Horde - ze12 map. (openGL) 
Issue History
2015-02-10 21:01FusedNew Issue
2015-02-10 21:07Edward-sanNote Added: 0011653
2015-02-10 21:25Edward-sanNote Edited: 0011653bug_revision_view_page.php?bugnote_id=11653#r6613
2015-02-11 02:10Edward-sanNote Added: 0011656
2015-02-11 02:11Edward-sanNote Edited: 0011656bug_revision_view_page.php?bugnote_id=11656#r6617
2015-02-11 14:00ibm5155Note Added: 0011657
2015-02-11 19:02Edward-sanNote Added: 0011659
2015-02-11 19:02Edward-sanNote Edited: 0011659bug_revision_view_page.php?bugnote_id=11659#r6619
2015-02-11 22:15Edward-sanNote Edited: 0011659bug_revision_view_page.php?bugnote_id=11659#r6620
2015-02-11 22:17Edward-sanNote Edited: 0011659bug_revision_view_page.php?bugnote_id=11659#r6621
2015-02-11 22:25Edward-sanNote Added: 0011660
2015-02-11 22:26ibm5155Note Added: 0011661
2015-02-11 22:32ibm5155Note Edited: 0011661bug_revision_view_page.php?bugnote_id=11661#r6623
2015-02-11 22:51Edward-sanNote Added: 0011663
2015-02-11 22:52Edward-sanNote Edited: 0011659bug_revision_view_page.php?bugnote_id=11659#r6624
2015-02-11 22:57Edward-sanNote Edited: 0011663bug_revision_view_page.php?bugnote_id=11663#r6626
2015-02-11 22:59ibm5155Note Added: 0011664
2015-02-11 23:02Edward-sanNote Edited: 0011663bug_revision_view_page.php?bugnote_id=11663#r6627
2015-02-11 23:03ibm5155Note Edited: 0011664bug_revision_view_page.php?bugnote_id=11664#r6629
2015-02-11 23:10ibm5155Note Edited: 0011664bug_revision_view_page.php?bugnote_id=11664#r6630
2015-02-11 23:15ibm5155Note Edited: 0011664bug_revision_view_page.php?bugnote_id=11664#r6631
2015-02-11 23:17Edward-sanNote Added: 0011665
2015-02-11 23:24Edward-sanNote Edited: 0011665bug_revision_view_page.php?bugnote_id=11665#r6633
2015-02-11 23:26Edward-sanNote Edited: 0011665bug_revision_view_page.php?bugnote_id=11665#r6634
2015-02-11 23:39ibm5155Note Added: 0011666
2015-02-11 23:55ibm5155Note Edited: 0011666bug_revision_view_page.php?bugnote_id=11666#r6636
2015-02-12 09:59Edward-sanNote Added: 0011667
2015-02-12 10:01Edward-sanNote Edited: 0011667bug_revision_view_page.php?bugnote_id=11667#r6638
2015-02-12 12:54ibm5155Note Added: 0011668
2015-02-12 13:25Edward-sanNote Added: 0011669
2015-02-12 13:40ibm5155Note Added: 0011671
2015-02-12 17:09ibm5155Note Added: 0011673
2015-02-12 18:44ibm5155Note Added: 0011674
2015-02-15 21:08DuskTarget Version => 2.0
2015-02-17 20:49ibm5155Note Edited: 0011674bug_revision_view_page.php?bugnote_id=11674#r6674
2015-02-18 12:21Edward-sanNote Added: 0011716
2015-02-22 21:00Torr SamahoNote Added: 0011739
2015-02-25 10:45ibm5155Note Added: 0011755
2015-02-25 12:58DuskNote Added: 0011757
2015-02-25 12:58DuskStatusnew => closed
2015-02-25 12:58DuskResolutionopen => no change required
2015-02-25 12:58DuskRelationship addedrelated to 0002114

Notes
(0011653)
Edward-san   
2015-02-10 21:07   
(edited on: 2015-02-10 21:25)
Indeed. I noticed also different texture alignment, but I wonder if it's because of the slope or not. This must be checked when this is fixed.


... and yes, please reduce the map so that it's possible to run it in gzdoom 900 (no zandronum/skulltag-specific scripts, no usage of skulltag resources, etc).

(0011656)
Edward-san   
2015-02-11 02:10   
(edited on: 2015-02-11 02:11)
Some news: I managed to run the extracted ze15.wad from zh-mappack10.pk3 into gzdoom; sadly, the issue happens also in gzdoom 900 and gzdoom trunk (and also in zdoom trunk). This must be reported over the zdoom bugs forum.

(0011657)
ibm5155   
2015-02-11 14:00   
Idk if it was already commented but here it goes..
The Dr Doctor Egypt ze map is also broken, but not related to slopes but yes the skybox looks like a big HOM bug.
The map that I'm talking is the ZE12
(0011659)
Edward-san   
2015-02-11 19:02   
(edited on: 2015-02-11 22:52)
The problems in ze15 started with zdoom r2138. This revision was already making problems with jumpix jpx27. Posted a bug report here.

[edit]Got a reply from graf:

Quote from "Graf Zahl"
Yes, same cause. They used a 'slope floor to here' thing with a line ID of 0.


Hence, sorry but ze15 must be changed with the suggestion of using non-0 line ID.

(0011660)
Edward-san   
2015-02-11 22:25   
@ibm5155, can you make a screenshot with the ze12 issue? The skybox works fine for me.
(0011661)
ibm5155   
2015-02-11 22:26   
(edited on: 2015-02-11 22:32)
Just when I finished to make a smaller ze15 with almost all missing things fixed :S

'http://www.mediafire.com/download/debh9u1lyqopwe1/ze15.pk3 [^]'

Uh change all slope ids D: that'll be a heaven work D:

EDIT: yes I can, here it goes...
IMG 1.3a'http://i.imgur.com/lHcoVA6.png [^]'
IMG 2.0a'http://i.imgur.com/ttfx4i0.png [^]'
IMG 1.3b'http://i.imgur.com/mDKKH9D.png [^]'
IMG 2.0b'http://i.imgur.com/djlJTDz.png [^]'
IMG 2.0c'http://i.imgur.com/b0kIgnj.png [^]'

(0011663)
Edward-san   
2015-02-11 22:51   
(edited on: 2015-02-11 23:02)
Which hardware do you have? can you reproduce on software renderer?

[edit]Oh, with my Intel + mesa, I see that the blue component is darkened, see'https://imgur.com/eSRXtBI [^]' .

[edit2] Can you make an example wad with that same skybox, so that I can check with gzdoom as well? Just extracting ze12.wad isn't enough to show the skybox.

(0011664)
ibm5155   
2015-02-11 22:59   
(edited on: 2015-02-11 23:15)
Software render works fine...

Also many times where I try to run zandronum in gl mode now, I only get a fatal error with this message: "R_OPENGL: No valid pixel formats found. Retrying in compatibility mode"

It didn't worked on my intel hd 4000 and amd hd8870m.

UP: the R_OPENGL fatal error only happens with intel hd4000, both of them are with their newest drivers.

Well, here's the rest of the setup

Windows 8.1 X64, intel core i7 3635QM, AMD HD8870m, 8gb DDR3 1,6GHz

[edit] I tried to run this in gl compatibility mode just to see what would happen and the effect is a bit different.

ZAN 2.0 gl comp'http://i.imgur.com/RdVvGzL.png [^]'

I also noted that in the normal gl config the bright skybox actually looks like when I'm too near to a texture, the texture will start to get extremly bright because of that


[edit2] actually, the same error message happens with the amd gpu, but on this case, it doesn't give me a fatal error...


Also here's the ze12 version (it just required to join ze12 and drresources wads)
ZE12 link here'http://www.mediafire.com/download/g3qn0nvegn2wjhn/ze12.pk3 [^]'

[EDIT3] The same effect happens on Gzdoom 1.8.02...

Zandronum 2.0 is having so many things with zombie horde maps O_o, like mine got 2 or 3 bugs on my own map that started to happen with 2.0 O_O

(0011665)
Edward-san   
2015-02-11 23:17   
(edited on: 2015-02-11 23:26)
Yup, I can confirm it happens also in gzdoom trunk. Reporting it at gzdoom forum.

[edit] Done.

Regarding the fatal error on load with your intel hd4000, which version of gzdoom fixed it? See this, starting from gzdoom 1.5.1 .

(0011666)
ibm5155   
2015-02-11 23:39   
(edited on: 2015-02-11 23:55)
Actually, it's working since the latest build.
I discovered that when I'm using more than one screen, it'll crash, but with a single screen it'll always work :D (weird, the same problem happens with battlefield 4)

[edit]Also, I discovered that on the same config, older gzdooms could run fine, since 1.4.06 things weren't running all the time and then after 1.4.07 it never worked (or maybe hardly ever would start)

1.5.01 crash
1.4.06 crash
1.4.07 some times works some times not
1.4.08 some times works some times not
1.4.05 some times works some times not
1.4.06 some times works some times not
1.4.03 works
1.4.02 works

(0011667)
Edward-san   
2015-02-12 09:59   
(edited on: 2015-02-12 10:01)
Quote
Actually, it's working since the latest build.

Do you mean gzdoom trunk build or latest gzdoom release?

Quote

1.5.01 crash
1.4.06 crash
1.4.07 some times works some times not
1.4.08 some times works some times not
1.4.05 some times works some times not
1.4.06 some times works some times not
1.4.03 works
1.4.02 works


The list is ordered not in the right way. Also, 1.4.06 is listed twice and it's inconsistent.

(0011668)
ibm5155   
2015-02-12 12:54   
I didn't tested the latest build I think, I just testes the latest build from your link'http://sourceforge.net/projects/zdoom/files/gzdoom/ [^]' (that is 1.8.02)

Indeed it's not, and idk why, but ording by date that's the order that I took from here'http://sourceforge.net/projects/zdoom/files/gzdoom/ [^]'

ehm, yeah, I duplicated the 06 one, I may have tested it twice :S
But from 1.4.05 it worked sometime but not all the time, it may be random, like on the first .06 test, I tested 6 times and all of them just gave me a fatal error, on the second try with 06 from the 6 tests, 3 started and 3 gave me a fatal error...
maybe 1.5.01 is still working sometimes too, but after .03 build It started to fail
(0011669)
Edward-san   
2015-02-12 13:25   
So it started to work in 1.8.02 and not for example in 1.6 or in 1.7.0?
(0011671)
ibm5155   
2015-02-12 13:40   
:| Well, I hope I can clarify what I'm trying to say.

Before 1.4.06 it worked just fine, after 1.4.03 it didn't worked quite well.

so the working list is :
1.4.03
1.4.02
1.4.01
...

and the ones that stoped working are:
1.8.02
...
1.5.01
1.4.06
1.4.07
1.4.08
1.4.05
1.4.06

I'm gonna test it more with the dev build too see if some of them fixed it.
(0011673)
ibm5155   
2015-02-12 17:09   
Test done, I still have a crash on the gzdoom build gzdoom-g2.1.pre-655-gc6cb849.7z, the latest one that I've found, Shall I post it on gzdoom forum?
(0011674)
ibm5155   
2015-02-12 18:44   
(edited on: 2015-02-17 20:49)
Edward Sam, since you have an intel gpu, can you test if it crashes if you run more than one display ?
EDIT:
I discovered that this two display fatal error was another dumb error from my driver kit, I just unpluged the hdmi cable, and pluged back and tadah, it's working fine...

Well since ze15 bug was a "map bug" but, the ze12 may be a bug, should this get splitted?

(0011716)
Edward-san   
2015-02-18 12:21   
Quote

Well since ze15 bug was a "map bug" but, the ze12 may be a bug, should this get splitted?


Absolutely yes.
(0011739)
Torr Samaho   
2015-02-22 21:00   
Did somebody already create a new ticket for the ze12 issues?
(0011755)
ibm5155   
2015-02-25 10:45   
done'http://zandronum.com/tracker/view.php?id=2114 [^]'
(0011757)
Dusk   
2015-02-25 12:58   
With ZE15 stuff deemed a map error and ZE12 stuff split to a new ticket, I figure we can close this.