[Helixhorned]

Diaz, on 05 February 2013 - 09:28 AM, said:

Is there a r_usenewshading value that looks exactly the same as setting its value to 1 before changing that cvar's behavior?

Yes, it is "1". The cvar's behavior wasn't changed, but a new mode "2" was introduced and made the default. Later, the default for r_shadescale was changed from 1.3 to 1.0. So, setting r_shadescale to 1.3 and r_usenewshading to 1 should give the pre-classic-fog-for-OpenGL look.

Diaz, on 05 February 2013 - 12:37 PM, said:

I've been using the Polymer renderer, and this probably happens since the introduction of the new shading code in r3303. My values are r_shadescale 1.3 and r_ ambientlight 1.25.

No matter if I set r_usenewshading to 1, 2, or 3, things apear lighter than they should, and it gets worse the darker the area is. I can't seem to get it to look 100% like before by tweaking the values in r_usenewshading, r_shadescale and r_ambientlight.

I can't reproduce this under Mapster32: the "r_usenewshading.map" test map looks the same throughout r3300..r3303 and SVN HEAD. By the way, r_ambientlight is a game-side variable and affects the global visibility, like DEFAULTVISIBILITY from CON (only reciprocally instead of multiplicatively). Maybe you were running mode 0 before? C programmers tend to start counting at zero, so the modes are
0 - old Polymost GL_EXP2 fog,
1 - the GL_EXP2 mode with tweaked constants that I first thought was an improvement, but was later shown to be deficient too and
2 - the new GL_LINEAR mode emulating the classic look.

[Diaz]

Alright, that worked. The problem was that I didn't notice changing r_shadescale doesn't take full effect until the map is restarted. Changing it to 1.3 from the start did the trick

[Micky C]

You can alternatively use r_restartvid to quickly and easy restart the renderer without losing anything.

[Diaz]

Yup, right. I just didn't notice r_shadescale was one of those commands requiring a map/vid restart; thought it had immediate effect, as the lighting in some objects seemed to change instantly when tweaking its value

[Fox]

Is it even remotely possible to make a model texture "panning"?

[Mikko]

Diaz, on 05 February 2013 - 06:02 PM, said:

Yup, right. I just didn't notice r_shadescale was one of those commands requiring a map/vid restart; thought it had immediate effect, as the lighting in some objects seemed to change instantly when tweaking its value

Hmmm, it seems to work fine here without a map/vid restart.

[Diaz]

With the Polymer renderer?

No big deal anyways, I just set the default to 1.3 and all is well

[Alan]

TerminX, on 31 January 2013 - 11:38 AM, said:

When it's done, CON code is only going to run on the server anyway (except for local display events and stuff like that). Mods will really need to be specifically designed for the new system (or heavily adapted, at least).

Have another tab in the startup window that asks for a server to connect to. When connected, a separate folder is set up where the client downloads the modified resources from the server.

[Micky C]

Mikko_Sandt, on 06 February 2013 - 03:30 AM, said:

Hmmm, it seems to work fine here without a map/vid restart.

For me it does need the restartvid. That was using polymer though. I think sprites seems to change instantly, however it's the map geometry that requires the restartvid.

Alan, on 06 February 2013 - 05:02 AM, said:

Have another tab in the startup window that asks for a server to connect to. When connected, a separate folder is set up where the client downloads the modified resources from the server.

I don't think you'll really have to download anything. At least with map files, when the host starts up a map, you can join it even though you don't have the map yourself. Although I'm not really sure about TCs, but then again you should really have the TC anyway before you start an online game for the actual TC.

[Alan]

You have to cache the files anyway. If you join a server with a map you don't have, you have to download the map to your cache.

[Plagman]

Fox, on 06 February 2013 - 03:18 AM, said:

Is it even remotely possible to make a model texture "panning"?

Not really, no. It would need to be an engine feature and would require the model to be UV-mapped a very specific way to work. What do you want to do?

[Fox]

I want to make the explosions model from Duke 64 exactly like they are in the ROM. Right now I am making them spin, but on reality it's just the texture that moves.

It would solve the problem if the spriteext x or y panning worked for the model textures. And it doesn't need to be a detailed effect, simply a "flat panning" of the texture.

I could reproduce the effect by having a set of multiple texture with a 1-px offset from each other, but that would be a ugly hack and would suck.

[Fox]

Phew, I am facing some trouble with events called multiple times. First of all, the events are run is reverse order, for example:

onevent EVENT_SPAWN
  ifactor PIGCOP
    spritepal 21
endevent

onevent EVENT_SPAWN
  ifactor PIGCOP
  ifspawnedby RECON
    spritepal 22
endevent

The intended effect would be that Pig Cops would have palette 21, except those spawned by a Recon Patrol Vehicle which would have palette 22. However this is not what actually happens, instead all Pig Cops would have palette 21 because the first onevent is called later.

The second problem is with the break command, which run across all the multiple onevent. Example below:

  onevent EVENT_SPAWN
    ifactor PIGCOP
      spritepal 21
  endevent

  onevent EVENT_SPAWN
    ifactor PIGCOP
      break
  endevent

This sample code is meant to make all Pig Cops have palette 21, but nothing will happen because of the break command in the second onevent. And I don't think this should happen, since when used in a state the break command only affects the code of the state.

[Helixhorned]

Fox, on 06 February 2013 - 06:47 PM, said:

Phew, I am facing some trouble with events called multiple times. First of all, the events are run is reverse order

That can be explained by the way they're implemented. When an endevent is encountered but the event was already defined previsouly, a JUMP instruction that points to the beginning of the old one is placed at the end of the new one. So yes, events defined later run earlier. [NOTE: jump shouldn't really be used by user CON code.]

Quote

onevent EVENT_SPAWN
  ifactor PIGCOP
    spritepal 21
endevent

onevent EVENT_SPAWN
  ifactor PIGCOP
  ifspawnedby RECON
    spritepal 22
endevent

The intended effect would be that Pig Cops would have palette 21, except those spawned by a Recon Patrol Vehicle which would have palette 22. However this is not what actually happens, instead all Pig Cops would have palette 21 because the first onevent is called later.

That code seems pretty artificial to me, and just having that logic in one "ifactor PIGCOP" branch in EVENT_SPAWN is much more readable IMO. The way I see it, event chaining is mainly a mechanism to allow modules to define independent behavior for a particular event. For example because each module needs EVENT_SPAWN for their custom actors.

Quote

The second problem is with the break command, which run across all the multiple onevent. Example below:

  onevent EVENT_SPAWN
    ifactor PIGCOP
      spritepal 21
  endevent

  onevent EVENT_SPAWN
    ifactor PIGCOP
      break
  endevent

This sample code is meant to make all Pig Cops have palette 21, but nothing will happen because of the break command in the second onevent. And I don't think this should happen, since when used in a state the break command only affects the code of the state.

Now this is interesting, and it can also be explained by what was said above: the two EVENT_SPAWN parts effectively become one block of code. I kind of agree that the expected behavior for break is "jump to end of event" (i.e. what is called "return" in most imperative programming languages). Shall we say that for now, "if a break is used inside an event that is multiply defined, the behavior is undefined"? (That is, one should not rely on it stay the same in the future.)

[Fox]

Helixhorned, on 07 February 2013 - 03:16 AM, said:

[NOTE: jump shouldn't really be used by user CON code.]

What do you mean? That I should not be opening an event multiple times, or that it's a sort of a mistake of Eduke?

Helixhorned, on 07 February 2013 - 03:16 AM, said:

That code seems pretty artificial to me

Fox, on 06 February 2013 - 06:47 PM, said:

for example:

You guessed it. But believe me, I have some pratical use for an event being opened multiple times.

Since the code is normally written from the top to the bottom, I think it's just natural to have the first event called first.

Helixhorned, on 07 February 2013 - 03:16 AM, said:

Shall we say that for now, "if a break is used inside an event that is multiply defined, the behavior is undefined"? (That is, one should not rely on it stay the same in the future.)

Ehh, since it is a basic function (like "else") can't it be fixed?

[Helixhorned]

Fox, on 07 February 2013 - 04:26 AM, said:

What do you mean? That I should not be opening an event multiple times, or that it's a sort of a mistake of Eduke?

I mean that jump should be avoided when writing CON code. There are some legitimate uses for what other languages call "goto" when jumping to error handling code forwards, but loops (=backward jumps) should be written using the available looping constructs: whilevarn or whilevarvarn.

Quote

Ehh, since it is a basic function (like "else") can't it be fixed?

Not immediately.

[Fox]

Well, I never really ever used the command jump, so that is not a problem for me.

[Mblackwell]

I'm not really sure how it's at all natural to not have your same actor called from multiple instances of an event?

I mean, for readability as well as the general logic of your code it doesn't seem to make much sense and it can potentially be a lot more lines of code depending on what you need done.

onevent EVENT_SPAWN
  ifactor PIGCOP
    spritepal 21
endevent

onevent EVENT_SPAWN
  ifactor PIGCOP
  ifspawnedby RECON
    spritepal 22
endevent

vs

onevent EVENT_SPAWN
    ifactor PIGCOP
    {
        ifspawnedby RECON
            spritepal 22
        else
            spritepal 21
    }
endevent

The above happens to be 9 lines just as before, but for each further EVENT_SPAWN you'll need an additional 3 lines (onevent EVENT_SPAWN - ifactor PIGCOP - endevent) along with whatever other if conditions you put in place. And all for code that logically should be happening before the actor is executing the rest of its code so it all fits together anyway.

[Plagman]

Keep in mind multiple event definitions are pretty important for stuff like mutators. We can't have stuff break or act weird just because you append a small CON mod using break in an event; it shouldn't need to have any knowledge of who else defined the event and what instructions they used inside it. If this is hard to get right, then it should just be an error to call break from any event, and I suspect that would be unacceptable.

[Fox]

Mblackwell, on 07 February 2013 - 07:26 AM, said:

I'm not really sure how it's at all natural to not have your same actor called from multiple instances of an event?

I mean, for readability as well as the general logic of your code it doesn't seem to make much sense and it can potentially be a lot more lines of code depending on what you need done.

onevent EVENT_SPAWN
  ifactor PIGCOP
    spritepal 21
endevent

onevent EVENT_SPAWN
  ifactor PIGCOP
  ifspawnedby RECON
    spritepal 22
endevent

vs

onevent EVENT_SPAWN
    ifactor PIGCOP
    {
        ifspawnedby RECON
            spritepal 22
        else
            spritepal 21
    }
endevent

The above happens to be 9 lines just as before, but for each further EVENT_SPAWN you'll need an additional 3 lines (onevent EVENT_SPAWN - ifactor PIGCOP - endevent) along with whatever other if conditions you put in place. And all for code that logically should be happening before the actor is executing the rest of its code so it all fits together anyway.

It is just an example. It doesn't need to make sense.

[Mblackwell]

Plagman, on 07 February 2013 - 10:00 AM, said:

Keep in mind multiple event definitions are pretty important for stuff like mutators. We can't have stuff break or act weird just because you append a small CON mod using break in an event; it shouldn't need to have any knowledge of who else defined the event and what instructions they used inside it. If this is hard to get right, then it should just be an error to call break from any event, and I suspect that would be unacceptable.

Break usually means "do not execute the following code block(s)". For the given example there's no real context other than perhaps order of operations. Unless we can specify that there's really not going to be a good way to do non-additive mutators.

[MusicallyInspired]

Got a problem with polymer on my laptop. My laptop is a decent build with a NVidia GeForce GT 550M 2GB video device. Polymer works fine and smoothly except for spotlights. In Mapster and ingame the spotlights don't show up at all. If I do 'restartvid' in the console the spotlight will appear for a splitsecond before disappearing again (also, I've noticed that it does not cast a shadow). I'm not sure if this was ever a problem before or not as I don't remember if I ever saw an ingame spotlight on my laptop or not. I guess I just assumed it would work. I'm already running the latest driver so that's not the problem. Any suggestions? I've tried the latest snapshot as well as the 64-bit build that was posted a little while back. No change. I'm not sure why it's not working as it's a decent NVidia card and NVidia is supposed to the best compatible device for polymer, right?

The eduke32.log file displays these lines of messages every time I typed in 'restartvid' if it means anything:

Quote

Initializing Polymer subsystem...
PR : Board loaded.
PR : FBO #1 initialization failed.
PR : FBO #2 initialization failed.
PR : FBO #3 initialization failed.
PR : FBO #4 initialization failed.
PR : FBO #5 initialization failed.
PR : Initialization complete in 180 ms.

[Fox]

I requested this before, but I think it is worth to mention it again. Is it possible to display the player start position as a sprite in Mapster?

What it looks like now:




What it could be like:

[Hendricks266]

Perhaps this could be implemented in a.m32?

[Fox]

How weird, I figured out there is a small bug with setgamepalette.

onevent EVENT_DISPLAYROOMS
  setplayer[THISACTOR].heat_on 1
  setgamepalette 0
  setplayer[THISACTOR].heat_on 0
endevent

By setting the game palette to zero, the game was supposed to display always display it regardless of the condition. However, because I changed the value of heat_on the palette is reset to 1 if the player is underwater and using Night Vision Goggles at the same time.

This is not a big issue, I have fixed the problems I was having by simply changing the order of the code... but I think it should at least be mentioned.

[Gambini]

Question: Is it possible that some TROR construction that works in Sofware, works in Polymost and obviously works in Polymer on a rig with a Nvidia video card, when tested in another computer with an ATI video card only works in Polymer and Software?

I know TROR is unsuported by Polymost. But I made a relatively simple construction that worked all three ways here, and when sent to this other guy he showed me some really ugly HOM screenshots. The only thing of why we think this could happen is the brand of our video cards.

[Fox]

I dunno, but I think it can't possible relate to the video card. The ROR glitches have something to do with the order which the render draw sectors. Polymer on the other hand make the levels entirely 3D, so ROR is not a problem.

[Mike Norvak]

Gambini, on 12 February 2013 - 10:17 AM, said:

Question: Is it possible that some TROR construction that works in Sofware, works in Polymost and obviously works in Polymer on a rig with a Nvidia video card, when tested in another computer with an ATI video card only works in Polymer and Software?

I know TROR is unsuported by Polymost. But I made a relatively simple construction that worked all three ways here, and when sent to this other guy he showed me some really ugly HOM screenshots. The only thing of why we think this could happen is the brand of our video cards.

Mhhh I remember having exactly the same problem while working on Metropolitan Starlight, The Big Cheese show me some ugly HOM TROR while I specially designed the area for Polymost and it looked good on my end... So finally we decided to make the map only Polymer playable.
Plagman must know.

[Gambini]

I´ve asked a couple of guys. They all had either HOM or glitches. It seems that you and me are the only ones able to see it. Interesting thing, if this trivia could be solved, it could be safe to say that TROR works on all three renderers at least to some degree.

[Plagman]

Hmm, that doesn't sound right to me. Nothing should be vendor specific in the core rendering. I don't understand why this would happen, except if Polymost TROR maybe relies on some non-conformant GL behavior which different drivers would then be free to interpret as they please.