[Jblade]

Just a quick question, how do I use mapster32 script to draw a line between 2 sprites with matching tags? I've tried to take a crack at it but I can't get it to work.

[Gambini]

I just installed the latest mapster32 snapshot for 64bits but when i fire it in windowed mode, it is way too high in the screen, hiding the top bar and a whole chunk of the tool itslef. Is there any way to position it so the bottom line of the window alligns the taskbar? I know this was possible with older snapshots (maybe with windowpositioning?) but i can´t even drag the top bar to place it properly because it´s hidden way up there where my screen doesn´t reach.

[Kyanos]

Right click taskbar select cascade windows.

Should do it for you.


(added;)

You can set the window position manually in mapster32.cfg

Line 59...

; Window positioning, 0 = center, 1 = memory
windowpositioning = 1
windowposx = 3
windowposy = 30

That will be top left corner.

[Jblade]

Does STAT_MIRROREDACTOR not work anymore? I vaguely remember seeing someone mention it a while ago; I tried to use it ingame but the statnum isn't being set by anything (or rather I have the sprite set up to log its statnum and there's no result matching STAT_MIRROREDACTOR )

[Fox]

It's only set during animatesprites for sprites displayed on mirrors.

[Jblade]

I know that, it doesn't work.

[Paul B]

I'm curious to know if the developers are still intending to release Eduke\Mapster updates? Or has Gearbox put a noose on such activity? Hasn't been any published updates in over a month and I find that kinda strange.

[Mblackwell]

It's because there's a big code refactoring happening behind the scenes that's not getting pushed until there's been a ton of testing. When that comes, coming with it are a decent number of bug fixes.

[Paul B]

Mblackwell, on 18 August 2016 - 12:58 PM, said:

It's because there's a big code refactoring happening behind the scenes that's not getting pushed until there's been a ton of testing. When that comes, coming with it are a decent number of bug fixes.

Thank you for the update! Looking forward to see what's around the corner. =)

[Danukem]

Hey guys, I just tried out EDuke32 r5829 64bit in order to test out one of my mods (Attrition). It wouldn't start and I found this error in the log:

ERROR: NULL weapon! WTF?! WEAPONzd_CLIP

The older snapshot works fine. I don't have time to investigate this, I'm just saying this is what happened.

[TerminX]

Yeah, it's actually a compiler bug. We're working on further changing the affected bits of the source to work around it.

[Tea Monster]

Something is definitely weird in how models are rendered in Polymer. Models appear correctly lit back in ver. 4593. In more recent versions (Can't remember the version No. But in August of this year), Models look very dark. This is not a model issue as the same models appear completely different in the two versions of the renderer.


Same model, same level, same lighting, different SVN version.

[Micky C]

That was the new feature introduced in 4596; the ethnic diversity shader.

[Tea Monster]

Diversity through programming, the wonders of modern technology!

[Mblackwell]

Tea Monster, on 04 September 2016 - 01:24 AM, said:

Something is definitely weird in how models are rendered in Polymer. Models appear correctly lit back in ver. 4593. In more recent versions (Can't remember the version No. But in August of this year), Models look very dark. This is not a model issue as the same models appear completely different in the two versions of the renderer.


Same model, same level, same lighting, different SVN version.

Er... can you narrow it down more?

There's there's about a thousand revisions since that one.

[Mark]

IIRC its gone back and forth a couple of times during that span. I've lost track of the various revisions brought up each time this has been a problem during that span.Sometimes a tweak was made and a revision worked better but still not quite right. I think his point was that its not a model problem which was a possibility during some of those discussions. I'm pretty sure TM has been in PMs with a couple of the devs descibing details.

From what I can gather, as soon as normal maps are applied ( with any settings ) the diff map refuses to illuminate from light sources.

[Mblackwell]

But if you can narrow it down to the first bad commit then they can work out the root of the problem.

Edit: You said 4593 was good. Try 4600 (for example).

[Mark]

Thats all "been there and done that" a few times already. The problem is elusive and we have people busy with other things and real life so a complete solution hasn't appeared. The people with the best chance of fixing it have the info from past posts and PMs on the subject.

The first bad commit was whatever came after 4593. And since then there have been a few attempts of fixes that were partially successful and then later on after another update it seemed broken again.

So other than 4593 and the next revision, there is not a clear cut case of "this version worked perfect and this one doesn't". There isn't an easy comparison to make for tracking purposes.

[Mblackwell]

The best chance really is to find the first bad commit.

If you send me a test setup I can bissect it.

[Mark]

4593 was the last working public revision. Start from there.

After 4593 there were a series of many dozens of uncommited revisions before the next public release. I went through this with Hendricks and we had it narrowed down to about a dozen or so IIRC. But then it got dropped for whatever reasons. I no longer remember the range he was checking last time. It was a long time ago.

[Tea Monster]

Mark narrowed down where the problem started, which version it was and all this has been forwarded to both TX and Plagman. We've been talking to them about this for a while now.

[Mblackwell]

Mark., on 04 September 2016 - 02:58 PM, said:

4593 was the last working public revision. Start from there.

After 4593 there were a series of many dozens of uncommited revisions before the next public release. I went through this with Hendricks and we had it narrowed down to about a dozen or so IIRC. But then it got dropped for whatever reasons. I no longer remember the range he was checking last time. It was a long time ago.

That's why I suggested r4600. It's the first revision with explicit changes to Polymer. If you send me a test case I can verify it and bug people about it.

[Hendricks266]

Can you forward the email chain to me or add me to that PM (or bump it if I already am)?

[Mark]

Tm should have that info.

I looked back through my PMs and there were multiple conversations spread out over time. One of them was concerning a framerate drop. It also by coincidence revolved around 4593 being the last good one.

Thats the one you and I were bisecting the crap out of.

[Jmoc]

I don't know if this is the right place to say that, but did you have a look at the "new" Duke Nukem 3D 20th anniversary?


Those lights reminds me of Polymer....

[Player Lin]

I guess everyones on Duke4.net should already know the weird textures with extra maps shit World Tour trailer.

[Tea Monster]

Yeah, and it isn't actually Polymer and has SFA to do with this thread.

[Jblade]

Any check of a userdef or something similar so we can detect if the player's using widescreen mode? Using it messes up the angle of skyboxes (I don't know enough about what widescreen actually changes beyond the immediate visual appearence of everything being 2x as tall so I can't really explain the issue well enough) so I need to figure out a way of making it work in both modes.

[Hendricks266]

xdim and ydim are available in CON, but are you asking for read access to r_usenewaspect?

Maybe your skybox problem is an oversight in the source. Could you show screenshots?

[Tea Monster]

Any progress on the dark rendering or the transparency problems?