New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

texture_top offset start point wrong #861

Open
matthiasmendler opened this Issue Apr 2, 2018 · 2 comments

Comments

Projects
None yet
1 participant
@matthiasmendler

matthiasmendler commented Apr 2, 2018

SLADE Version: (3.1.2.4)
Operating System: (Linux)

Issue Details:
EDIT: I made some mistakes in the first report. Fixed now.

I don' t know the right terminology, but I think these screenshots explain the problem

SW1GRAY, the dark switch, is texture_mid
SW2GRAY, the bright switch is texture_top

texture_mid from scaley=1.00 in 0.10 increasements until scaley=1.50.
In Slade:
auswahl_037
In GZDOOM:
auswahl_039
Everything is fine. The texture begins in the top and gets scaled from there.

as texture_top from scaley=1.00 in 0.10 increasements until scaley=1.50.
In Slade:
grafik
In GZDOOM:
grafik

Slade scales the texture from the middle of the height, while gzdoom does it from the bottom.

@matthiasmendler matthiasmendler changed the title from Upper Unpegged, uneven scaled texture different offset in slade and gzdoom to texture_top offset start point wrong Apr 8, 2018

@matthiasmendler

This comment has been minimized.

Show comment
Hide comment
@matthiasmendler

matthiasmendler commented Apr 8, 2018

Here is the wad:
testmap2.zip

@matthiasmendler

This comment has been minimized.

Show comment
Hide comment
@matthiasmendler

matthiasmendler Apr 8, 2018

Well, I was looking into it myself. I posted some really bad solution before but deleted it, now here is a slightly better hack.
Please don't kill me ;) My c++ skills are quite rudimentary, I never did anything like this before, never used opengl, and I also only used github to get source code so far. So I forked this project for two lines of code. But I feel it's too dirty for a pull request.

matthiasmendler@017b507

matthiasmendler commented Apr 8, 2018

Well, I was looking into it myself. I posted some really bad solution before but deleted it, now here is a slightly better hack.
Please don't kill me ;) My c++ skills are quite rudimentary, I never did anything like this before, never used opengl, and I also only used github to get source code so far. So I forked this project for two lines of code. But I feel it's too dirty for a pull request.

matthiasmendler@017b507

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment