Zandronum Chat on our Discord Server Get the latest version: 3.2
Source Code
My View | View Issues | Change Log | Roadmap | Zandronum Issue Support Ranking | Rules | My Account
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0002098Zandronum[All Projects] Bugpublic2015-02-10 21:012015-02-25 12:58
ReporterFused 
Assigned To 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformMicrosoftOSWindowsOS Version8
Product Version2.0-beta 
Target Version2.0Fixed in Version 
Summary0002098: Latest build causes slope and height malfunctions in Zombie Horde.
DescriptionAs found while testing, on map ze15 most of the map will bug and cause sectors to change height and perhaps even slope.
Steps To ReproduceBuild:'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

Additional Information1.3:'http://prntscr.com/63imuw [^]'
2.0:'http://prntscr.com/63immo [^]'
___________
1.3:'http://prntscr.com/63ina0 [^]'
2.0:'http://prntscr.com/63ini9 [^]'
Attached Files

- Relationships
related to 0002114closedEdward-san Latest build causes skybox hom in Zombie Horde - ze12 map. (openGL) 

-  Notes
User avatar (0011653)
Edward-san (developer)
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).
User avatar (0011656)
Edward-san (developer)
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.
User avatar (0011657)
ibm5155 (reporter)
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
User avatar (0011659)
Edward-san (developer)
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.
User avatar (0011660)
Edward-san (developer)
2015-02-11 22:25

 @ibm5155, can you make a screenshot with the ze12 issue? The skybox works fine for me.
User avatar (0011661)
ibm5155 (reporter)
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 [^]'
User avatar (0011663)
Edward-san (developer)
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.
User avatar (0011664)
ibm5155 (reporter)
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
User avatar (0011665)
Edward-san (developer)
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 .
User avatar (0011666)
ibm5155 (reporter)
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
User avatar (0011667)
Edward-san (developer)
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.
User avatar (0011668)
ibm5155 (reporter)
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
User avatar (0011669)
Edward-san (developer)
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?
User avatar (0011671)
ibm5155 (reporter)
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.
User avatar (0011673)
ibm5155 (reporter)
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?
User avatar (0011674)
ibm5155 (reporter)
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?
User avatar (0011716)
Edward-san (developer)
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.
User avatar (0011739)
Torr Samaho (administrator)
2015-02-22 21:00

 Did somebody already create a new ticket for the ze12 issues?
User avatar (0011755)
ibm5155 (reporter)
2015-02-25 10:45

 done'http://zandronum.com/tracker/view.php?id=2114 [^]'
User avatar (0011757)
Dusk (developer)
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.

Issue Community Support
This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.
Supporters: Hypnotoad DrinkyBird ibm5155
Opponents: No one explicitly opposes this issue yet.

- Issue History
Date Modified Username Field Change
2015-02-10 21:01 Fused New Issue
2015-02-10 21:07 Edward-san Note Added: 0011653
2015-02-10 21:25 Edward-san Note Edited: 0011653 View Revisions
2015-02-11 02:10 Edward-san Note Added: 0011656
2015-02-11 02:11 Edward-san Note Edited: 0011656 View Revisions
2015-02-11 14:00 ibm5155 Note Added: 0011657
2015-02-11 19:02 Edward-san Note Added: 0011659
2015-02-11 19:02 Edward-san Note Edited: 0011659 View Revisions
2015-02-11 22:15 Edward-san Note Edited: 0011659 View Revisions
2015-02-11 22:17 Edward-san Note Edited: 0011659 View Revisions
2015-02-11 22:25 Edward-san Note Added: 0011660
2015-02-11 22:26 ibm5155 Note Added: 0011661
2015-02-11 22:32 ibm5155 Note Edited: 0011661 View Revisions
2015-02-11 22:51 Edward-san Note Added: 0011663
2015-02-11 22:52 Edward-san Note Edited: 0011659 View Revisions
2015-02-11 22:57 Edward-san Note Edited: 0011663 View Revisions
2015-02-11 22:59 ibm5155 Note Added: 0011664
2015-02-11 23:02 Edward-san Note Edited: 0011663 View Revisions
2015-02-11 23:03 ibm5155 Note Edited: 0011664 View Revisions
2015-02-11 23:10 ibm5155 Note Edited: 0011664 View Revisions
2015-02-11 23:15 ibm5155 Note Edited: 0011664 View Revisions
2015-02-11 23:17 Edward-san Note Added: 0011665
2015-02-11 23:24 Edward-san Note Edited: 0011665 View Revisions
2015-02-11 23:26 Edward-san Note Edited: 0011665 View Revisions
2015-02-11 23:39 ibm5155 Note Added: 0011666
2015-02-11 23:55 ibm5155 Note Edited: 0011666 View Revisions
2015-02-12 09:59 Edward-san Note Added: 0011667
2015-02-12 10:01 Edward-san Note Edited: 0011667 View Revisions
2015-02-12 12:54 ibm5155 Note Added: 0011668
2015-02-12 13:25 Edward-san Note Added: 0011669
2015-02-12 13:40 ibm5155 Note Added: 0011671
2015-02-12 17:09 ibm5155 Note Added: 0011673
2015-02-12 18:44 ibm5155 Note Added: 0011674
2015-02-15 21:08 Dusk Target Version => 2.0
2015-02-17 20:49 ibm5155 Note Edited: 0011674 View Revisions
2015-02-18 12:21 Edward-san Note Added: 0011716
2015-02-22 21:00 Torr Samaho Note Added: 0011739
2015-02-25 10:45 ibm5155 Note Added: 0011755
2015-02-25 12:58 Dusk Note Added: 0011757
2015-02-25 12:58 Dusk Status new => closed
2015-02-25 12:58 Dusk Resolution open => no change required
2015-02-25 12:58 Dusk Relationship added related to 0002114




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker