[Micky C]

He's not referring to content made for polymer per se. He meant that polymer had certain limitations and bugs that rendered things incorrectly when compared to both classic and polymost. I've mentioned the multiple skyboxes in one map before:

Micky C, on 13 December 2015 - 11:40 PM, said:

...I'm hoping that it'll include support for multiple paralaxed skies in a map after all this time (and by extension the showview command if I'm remembering it correctly). The lack of the latter has broken many features in mods.

[icecoldduke]

Micky C, on 27 December 2015 - 09:35 PM, said:

He's not referring to content made for polymer per se. He meant that polymer had certain limitations and bugs that rendered things incorrectly when compared to both classic and polymost. I've mentioned the multiple skyboxes in one map before:

I don't see a reason why we can't support multiple skyboxes in one map(as long as they both aren't in view at the same time), but we'll have to deal with these issues on a case by case basis.

[Hendricks266]

Polymer not supporting multiple skyboxes is absolutely a bug that should be eradicated. Plagman knows exactly what the issue is, and fixing it would also fix showview.

[icecoldduke]

Hendricks266, on 27 December 2015 - 10:09 PM, said:

Polymer not supporting multiple skyboxes is absolutely a bug that should be eradicated. Plagman knows exactly what the issue is, and fixing it would also fix showview.

I haven't looked into the issue at all yet. Polymer's build content to 3d code is pretty nice and easy to understand, which is why I'm using it in PolymerNG(just with all the OpenGL stuff ripped out). I'm sure we'll have to deal with Polymer specific issues in PolymerNG, but I don't know the extent of those bugs yet, I'll ask Plagman if he can pass along the info to me.

Since Polymer used the tessellation code in the GLU library(libtess), I took the libtess code from Mesa's GLU code and included it in the build project(the license is compatible). I did that so the code is more portable.

[Mblackwell]

icecoldduke, on 27 December 2015 - 09:41 PM, said:

(as long as they both aren't in view at the same time)

The original game can display any number of skies simultaneously.

[icecoldduke]

Mblackwell, on 27 December 2015 - 11:47 PM, said:

The original game can display any number of skies simultaneously.

What would be your use case?

[Danukem]

icecoldduke, on 28 December 2015 - 04:50 AM, said:

What would be your use case?

Let's say you are in a house on a mountain top. If you look out the windows to the north you city a city scape, while to the east you see ocean, mountains to the south and desert to the west. By facing the corners of the room you could see two skyboxes at a time.

[icecoldduke]

Trooper Dan, on 28 December 2015 - 10:36 AM, said:

Let's say you are in a house on a mountain top. If you look out the windows to the north you city a city scape, while to the east you see ocean, mountains to the south and desert to the west. By facing the corners of the room you could see two skyboxes at a time.

Maybe I'm failing to understand the issue, but couldn't you do that with one skybox?

[Kyanos]

icecoldduke, on 30 December 2015 - 11:48 AM, said:

Maybe I'm failing to understand the issue, but couldn't you do that with one skybox?

Not necessarily. Lets say a classic usermap did this with builds normal parallax sky, shouldn't your renderer be backwards compatible to draw multiple skies just like regular old Duke3D? I think one of the Red maps did this IIRC.

[Kyanos]

And about Dans original example, what if instead of windows on the mtn top building, they were big open doors. The player could walk through any one of four doors into a completely different world... Anythings possible in build.

[Mark]

At first I thought the same thing. Make a custom skybox that will show different terrain depending on which direction you will look out the window or whatever. But then I realized that if your view out one of the windows is wide enough you will see bleedover from another side of the skybox. So I can see why in limited circumstances multiple skyboxes would be handy. Personally, I don't think I need it but maybe I'm not creative enough for the use of it.

[Mblackwell]

Classic maps/usermaps use multiple parallax skies. My use case is not breaking two decades of content and reducing engine functionality. The fact that it's not possible in Polymer is a bug.

[Fox]

Mblackwell, on 27 December 2015 - 11:47 PM, said:

The original game can display any number of skies simultaneously.

Yes, but it's a understandable limitation of a 3D rendering engine. It's a priority to make it at least display different skies not simultaneously to support the original levels.

[Micky C]

IIRC Plagman said it was just a matter of making the renderer do an additional rendering pass do show the additional skies.

However let's not forget that the showview con command also needs to work correctly in polymerNG. The fix will kill two birds with one stone.

[icecoldduke]

Micky C, on 30 December 2015 - 02:17 PM, said:

IIRC Plagman said it was just a matter of making the renderer do an additional rendering pass do show the additional skies.

However let's not forget that the showview con command also needs to work correctly in polymerNG. The fix will kill two birds with one stone.

Yeah it shouldn't be a complicated fix, but I will have to assign it a low priority for right now.

[Plagman]

It's the opposite: right now Polymer does an additional rendering pass, drawing a sky box / sky cylinder for whatever sky it thinks needs to be displayed (really the first parallax ceiling it ever finds in the map), and then renders the map on top of that, leaving holes in place of any parallaxed ceilings and floors. What it needs to do instead is to render parallaxed ceilings and floors using their real floor/ceiling data as part of the regular map pass (what classic and Polymost do), with a parallaxed / skybox material instead, and only leave holes in the map for things that are really holes, eg. what people do with showview portals right now. The early sky pass is what obscures the showview pass, as it always covers the whole screen.

[icecoldduke]

Plagman, on 02 January 2016 - 01:30 PM, said:

It's the opposite: right now Polymer does an additional rendering pass, drawing a sky box / sky cylinder for whatever sky it thinks needs to be displayed (really the first parallax ceiling it ever finds in the map), and then renders the map on top of that, leaving holes in place of any parallaxed ceilings and floors. What it needs to do instead is to render parallaxed ceilings and floors using their real floor/ceiling data as part of the regular map pass (what classic and Polymost do), with a parallaxed / skybox material instead, and only leave holes in the map for things that are really holes, eg. what people do with showview portals right now. The early sky pass is what obscures the showview pass, as it always covers the whole screen.

That sounds what I would have done for skies, just render the skybox first, and the level geo after without the parallax floor/ceiling. I'm going to assign the bug as P3(aka low priority) right now.

[Kyanos]

Quote

leaving holes in place of any parallaxed ceilings and floors

This here is more the issue on my end than multiple skies. A lot of sector geometry from outside the current players area leaks through these holes, in Polymer you can see things from adjacent sectors above a sky, things that do not get rendered in classic or polymost.

[Mark]

That is why Decay uses version 5293 from July. Anything after that was occasionally "leaking". Its a known thing. Although now that I think about it I have run into it before. But it might have been due to my mapping errors. Don't know for sure.

[Kyanos]

This is a good example of what I mean.



>map:  polymer_test.zip (728bytes)
Number of downloads: 232

Mark., on 03 January 2016 - 08:42 AM, said:

That is why Decay uses version 5293 from July. Anything after that was occasionally "leaking". Its a known thing. Although now that I think about it I have run into it before. But it might have been due to my mapping errors. Don't know for sure.

That revision is much better, thanks for the link. It's still not perfect, it's showing only one error in my test map.

[icecoldduke]

Drek, on 03 January 2016 - 09:28 AM, said:

This is a good example of what I mean.

polymer_test.png

>map: polymer_test.zip


That revision is much better, thanks for the link. It's still not perfect, it's showing only one error in my test map.
duke0021.png

When I get a chance I'll create a bug for it and include all the info you provided.

[icecoldduke]

Can someone make a list of all the wierd Polymer bugs they would LIKE to see POSSIBLY fixed in PolymerNG?

[Mark]

first one that comes to mind is the SE49 point lights will bleed through walls into adjacent sectors

[Tea Monster]

How hard-coded lights like switches and fire shine through meshes.

That weird 'noisey' quality that polymer models seem to have. It's impossible to get stuff to look crisp and clear.

[Mark]

Not sure if its considered a bug or not. A 2D sprite will be lit by a Polymer light on one side but if you rotate the sprite 180 degrees it does not light up.

[Micky C]

Actors (or at least the player) case a shadow as though the sprite is one-sided and wall-aligned. I.e if you're in front of the light it looks fine, but if you're standing to the left or right of the source you approach a 1D (or no shadow), and the shadow disappears if you're standing anywhere behind the source of the light. I don't know how the directions are taken into account, i.e whether it's global or light-specific.

[Steveeeie]

[icecoldduke]

A couple people have messaged me asking me what's going on, I'm out for the next couple of weeks due to a RL issue, I'll be back in full swing end of this month.

[supergoofy]

NVIDIA Vulkan Driver Support (Driver 356.39 Beta)
https://developer.nv...m/vulkan-driver

I haven't tested it, because I have older GPU


[edit]

AMD Radeon Software Beta for Vulkan Version 16.15.1009
http://support.amd.c...ulkan-Beta.aspx

[MusicallyInspired]

Ah, mine's too old too. Too bad.