Big issue with latest Mapster build (r5568)

blizzart

#1 Posted 16 January 2016 - 01:36 PM

Hi everybody,

I just wanted to work on a map, but I have a big problem with the latest EDuke-version (r5568 / 64bit / Win 8.1).

Maybe it is just me, but perhaps anyone else can confirm this behavior:

The realtime wall manipulation doesn´t work for me in 3D mode. This means neither stretching, panning or shading of a wall does show any effect in 3Dmode while doing it. I have to go to 2Dmode and back to 3Dmode to see any changes which makes it nearly impossible to work.

Panning/Shading of floors and ceilings work as usual.

The mapster32.log doesn´t show anything related to this issue.

TerminX

el fundador

#2 Posted 16 January 2016 - 01:40 PM

Are you using Polymer by any chance?

Mark

#3 Posted 16 January 2016 - 01:50 PM

Problem is in Polymer only for me.

blizzart

#4 Posted 16 January 2016 - 02:28 PM

TerminX, on 16 January 2016 - 01:40 PM, said:

Are you using Polymer by any chance?

Yes I do.

TerminX

el fundador

#5 Posted 16 January 2016 - 04:35 PM

I'm not able to reproduce it.

Mark

#6 Posted 16 January 2016 - 04:39 PM

I'm running 5568 32 bit under Vista with an Nvidia 750ti card. I'll try older versions to see if I can find where the problem starts. Its very recent because I had been using something from a month ago or less just fine. So far 5548 is bad.... 5513 is bad.... 5501 is bad....

Its longer than I thought. I'll post again when I have it nailed down.

This post has been edited by Mark.: 16 January 2016 - 04:49 PM

blizzart

#7 Posted 16 January 2016 - 04:58 PM

Mark., on 16 January 2016 - 04:39 PM, said:

The former version I was running with Polymer was r5409 (64bit) and this was working without any problems.

Wait. r5495 also has this problems but it applies the changes to the wall in 3Dmode when you lower or increase the height.

I can reproduce it with different mods and a clean copy of DN3D. Also on my NVidia GT635M and the Intel HD4000 chipset.

Mark

#8 Posted 16 January 2016 - 04:58 PM

That took way longer than expected. 5474 good... 5491 and higher bad

There are no other versions in between.

This post has been edited by Mark.: 16 January 2016 - 04:59 PM

blizzart

#9 Posted 16 January 2016 - 05:02 PM

blizzart, on 16 January 2016 - 04:58 PM, said:

Wait. r5495 also has this problems but it applies the changes to the wall in 3Dmode when you lower or increase the height.

Just gave it a quick try, r5568 behaves the same way.

[EDIT] The mentioned issue ONLY affects white-lined walls, red line walls of child sectors can be edited without any problems.

This post has been edited by blizzart: 16 January 2016 - 05:20 PM

Mark

#10 Posted 25 January 2016 - 03:26 PM

I need a few more people to verify this problem so that it can get some attention. TX says its not happening on his end so we need to show that more people are having this issue. So far only Blizzart and I have noticed the glitch.

Starting with version 5491 and higher, in Mapster and using Polymer, when you try to adjust x or y panning on a white wall it looks like nothing happens. But if you switch to 2D and back to 3D mode NOW the change shows.

This post has been edited by Mark.: 25 January 2016 - 03:44 PM

blizzart

#11 Posted 25 January 2016 - 04:47 PM

[quote name='Mark.' timestamp='1453764380' post='238077']
I need a few more people to verify this problem so that it can get some attention. TX says its not happening on his end so we need to show that more people are having this issue. So far only Blizzart and I have noticed the glitch.

Starting with version 5491 and higher, in Mapster and using Polymer, when you try to adjust x or y panning on a white wall it looks like nothing happens. But if you switch to 2D and back to 3D mode NOW the change shows.

What I have also noticed so far (beside what Mark wrote) in short.

- Glitch only affects white walls
- Raising / lowering the ceiling and the changes appear
- beside panning it also affects stretching and shading
- happens with nVidia GT635M and Intel HD4000 on my end

Mark

#12 Posted 25 January 2016 - 06:14 PM

Even though its been a problem for the last couple of months and not discovered until recently is probably because not a lot of mappers are using Polymer and the ones that do ( including me ) don't always update to the latest version right after it's release.