[Reaper_Man]

This setup will break down the more a mod changes the vanilla code, particularly the APLAYER code. A mod that totally does away with things like PFROZEN and PSHRINKING will throw CON errors. Or a mod that uses a different define name for the timer than THAWTIME won't ever display properly.

I am pretty sure that stepping into a blue light sector wouldn't trigger "if sprite[].pal" type checks, since technically the actor's tsprite is having its palette changed and not the actual sprite itself. (Without going super in-depth, the tsprite is a virtual sprite for every sprite/actor in a map and handles the visual component independent of the actual actor, for example enemies turning PAL 6 with nightvision don't actually change palettes, but their tsprite does.) Anyway, it should be easy to test that real quick.

Looking at the vanilla behavior for freezer-ing, aside from starting action PFROZEN, the only other characteristic you could check against would be the palette.

[NightFright]

That's what I thought. I was looking through the entire wiki and couldn't find another method. At first I hoped I could use sprite[].htg_t 4 PFROZEN, but I'd need a variable instead of an action here.

Before I am looking for a map with fitting conditions it'd probably be faster to create a super simple map with a mirror and pal 1 lighting. In any case, it'd be a very specific case, especially since it's rather unlikely to get frozen in singleplayer (only with mods, basically) and even then, you'd have to die while frozen in blue light.

[ck3D]

You wouldn't even need a mirror in your test map, the freezer projectiles bounce off all wall types. (edit - didn't notice the post was over a week old before I replied, so you've probably remembered or found out since)

[lllllllllllllll]

Is it ok to use the same var or even RETURN as a throwaway for unwanted return vars?

For example hitscan has 6 return vars
<hit sector return var> <hit wall return var> <hit sprite return var> <hit x return var> <hit y return var> <hit z return var>
when only wanting a sprite id
TEMP1 TEMP1 TEMP2 TEMP1 TEMP1 TEMP1


It did not cause any apparent crashes, lag, errors, or otherwise

[Reaper_Man]

Yes.

Well, probably not RETURN as that's a pre-defined gamevar and may have strange or unintended results overriding its value. But using a user gamevar like TEMP1 like this is just fine. Strictly speaking, the value will result in the value of "hit z return var" as it's assigned last.

[lllllllllllllll]

Why is "ife" for the current picnum breaking loops?

//loop ends after 1 sprite
//
        whilen SECTORVAR NUMSECTORS
        {
          headspritesect PICNUMVAR SECTORVAR
          set PICNUMCOPY PICNUMVAR
          whilen PICNUMVAR -1
          {
            ife PICNUMVAR RESPAWN //<
              ife sprite[].hitag sprite[PICNUMVAR].lotag
                setav[PICNUMVAR].TEMP1 1
            nextspritesect PICNUMVAR PICNUMVAR
            ife PICNUMVAR PICNUMCOPY
              set PICNUMVAR -1
          }
          add SECTORVAR 1
        }
//


//loop ends after all sprites
//
        whilen SECTORVAR NUMSECTORS
        {
          headspritesect PICNUMVAR SECTORVAR
          set PICNUMCOPY PICNUMVAR
          whilen PICNUMVAR -1
          {
	    switch sprite[PICNUMVAR].picnum //<
	     case RESPAWN  //<
              ife sprite[].hitag sprite[PICNUMVAR].lotag
                setav[PICNUMVAR].TEMP1 1
	      break
	    endswitch
            nextspritesect PICNUMVAR PICNUMVAR
            ife PICNUMVAR PICNUMCOPY
              set PICNUMVAR -1
          }
          add SECTORVAR 1
        }
//

[Danukem]

lllllllllllllll, on 08 June 2024 - 05:53 AM, said:

Why is "ife" for the current picnum breaking loops?

//loop ends after 1 sprite
//
        whilen SECTORVAR NUMSECTORS
        {
          headspritesect PICNUMVAR SECTORVAR
          set PICNUMCOPY PICNUMVAR
          whilen PICNUMVAR -1
          {
            ife PICNUMVAR RESPAWN //<
              ife sprite[].hitag sprite[PICNUMVAR].lotag
                setav[PICNUMVAR].TEMP1 1
            nextspritesect PICNUMVAR PICNUMVAR
            ife PICNUMVAR PICNUMCOPY
              set PICNUMVAR -1
          }
          add SECTORVAR 1
        }
//


//loop ends after all sprites
//
        whilen SECTORVAR NUMSECTORS
        {
          headspritesect PICNUMVAR SECTORVAR
          set PICNUMCOPY PICNUMVAR
          whilen PICNUMVAR -1
          {
	    switch sprite[PICNUMVAR].picnum //<
	     case RESPAWN  //<
              ife sprite[].hitag sprite[PICNUMVAR].lotag
                setav[PICNUMVAR].TEMP1 1
	      break
	    endswitch
            nextspritesect PICNUMVAR PICNUMVAR
            ife PICNUMVAR PICNUMCOPY
              set PICNUMVAR -1
          }
          add SECTORVAR 1
        }
//

PICNUMVAR is a sprite number and is NOT the picnum of the sprite. In the second loop, you do a switch statement on the picnum, but in the first loop you just compare the sprite number directly with RESPAWN, so if the sprite number happens to be 9 that will be true. That doesn't necessarily explain why the loop ends early, but it seems like it invalidates the first version regardless. Beyond that mistake, I have couple of criticisms. First, your variable names are obscuring what is going on rather than helping you. I think when you gave it the name PICNUMVAR you convinced yourself that it holds a picnum --- but of course you can put any value at all in it and in this case it's not a picnum. It's better to refer directly to the struct members whenever possible rather than putting values in variables. Secondly, you could have figured out what is going on by logging values, rather than looking at the problem like it was test question. You are eventually going to come across bugs that you won't be able to figure out unless you can log what is going on at specific points in the code.

[lllllllllllllll]

Thank you, I did something retarded again

[VGames]

Is the animation code for the fist that hits the nuke button at the end of a map available anywhere? I'm referring to the one that plays when EVENT DISPLAYFIST is triggered. I noticed it was not in the samples file that has all of the weapon and view animations like the cracking knuckles animation.

[quakis]

I'm looking into coding a 3D Skybox much in the same style as the one seen in Ion Fury, something with a camera/anchor point that's able to render 1:1 and align with the mapping terrain. I've looked through the code in IF but not certain I've caught all the details how it works, the code from AWOL also gave me some additional insight but I think it functions a little different compared to IF's?

What kind of full checklist am I looking at to meet all the required steps to get something like this at least in a working state to later expand from?

This is how I think the checklist would look based on my understanding:

• a camera origin actor, get and store its xyz etc coords
  
• an anchor point actor, get and store its xyz etc coords
  
• link camera origin with anchor point to keep position tied together (not yet certain how to just yet)
  
• skybox ceiling / wall picnum replaced with an empty picnum (replaced with HOM/NULL) so stuff can be rendered behind it?
  
• initialise all the above via EVENT_ENTERLEVEL
  
• get the camera viewpoint (via showviewunbiased / showviewq16unbiased?)
  
• draw camera viewpoint where HOM / NULL is (via EVENT_DISPLAYROOMS?)
  
• ???

I honestly might be way over my head for this one right now with my current knowledge, but feel it's an important part of the design for my current project. I could use a TROR layer as a backup option but that's not really suitable for my needs here.

I'd rather go into this knowing what I might need for the whole thing. Using the above process and keeping it simple one step at a time, I looked into just replacing the defined skybox picnum with null. Already hit a roadblock when Eduke fails to enter any map (regardless if skybox picnum used or not) after it finishes loading and then quits out. I'm definitely missing some prior steps or still need to add more parts first to avoid that.

Which is why I thought its better to ask about the possible checklist involved before digging myself into a hole and learn nothing from it all.

Cheers for your time.

[Danukem]

This is one of the few effects I haven't done yet in one of my mods, although I've coded similar things (most notably the flying ship effect in Demon Throne where everything you see around the ship is projected from a moving camera).


My advice would be to get the most basic version of the effect working first without worrying about anchor points at all. Make a map with a HOM area where the sky would be, make a big separate room in it with the scene you want to show for the sky, then use showview in EVENT_DISPLAYROOMS to show that in place of the HOM sky. It will look weird as you are walking around without the anchor point code but the simple version will be much easier to set up and will teach you how the effect works.

[quakis]

Thanks Dan, guess I'm overcomplicating things for myself at this stage. I'll start with your advice and see how I get on, at least I know the anchor points won't be necessary just yet to play around with this effect. Cheers!

[ck3D]

As far as how it's done in A.W.O.L. it's mainly Reaper_Man you should ask. The Dubai map I made uses a switchable camera system. The skybox is built on an exact 1:32 scale so that it aligns with the other two (playable) layers of the city (that actually was the hardest part, getting the map/skybox/back to map transitions seamless), where both rooftop and street level are connected through the skybox with traditional silent teleporters; the miniature has two skybox viewpoints/cameras, one at street level, another one at sky; each sector in which a transition can happen (usually the transport elevators found inside the buildings) has a special effector in it that triggers a change of camera that most of the time is invisible as the player is indoors, or falling when it happens. The switchable camera as a feature was introduced specifically for that level and is additional to the more traditional skybox system so that the skybox can be 'sandwiched' in the middle of the map's z axis in addition to surrounding it.

[Reaper_Man]

quakis, on 22 June 2024 - 12:52 PM, said:

Using the above process and keeping it simple one step at a time, I looked into just replacing the defined skybox picnum with null. Already hit a roadblock when Eduke fails to enter any map (regardless if skybox picnum used or not) after it finishes loading and then quits out.

Can you post your error log? That seems like something is really wrong.

Conceptually I think you understand how it's done. The effect works by abusing the hall-of-mirrors "error" and rendering a "sky camera" to the screen prior to all other rendering. This way any visible HOM textures render the camera's perspective. The "skybox" effect is then built by moving and rotating the sky camera's position relative to the player. In AWOL, the "sky camera" is placed in the centerpoint of the 3D skybox area, and is used as the relative reference point to the actual game world's origin (0, 0) position.

In your checklist, the "camera origin actor" is just the player, or whatever is the current active game view. The math to "link" the player view to the skybox camera is just a matter of 1.) dividing the player's absolute position by your skybox scale, and then 2.) applying that position as an offset from the sky camera's position. So if your sky camera scale is 1/10, and the player is currently at XY coords 150,250, and your sky camera is located at 1000,1000, then the result camera rendering position is 1015,1025. This is performed in EVENT_DISPLAYROOMS in the file "awol_env.con", along with the actual rendering. You want to use the "q16" versions of things because you get greater integer precision, which removes jitter in the camera view, even if you are using a scale of 1:1