[Danukem]

You can turn it invisible in EVENT_EGS and then make it visible one tic later in EVENT_GAME. You should also be able to use defineprojectile and set cstat to 32768 in the definition and then set it to visible one tic later. I know with certainty that the first method works because I use it sometimes.

[lllllllllllllll]

onevent EVENT_EGS
  ifactor myprojectile
    cstator 32768
endevent

onevent EVENT_EGS
  ifactor myprojectile
    setactor[THISACTOR].cstat 32768
endevent

onevent EVENT_EGS
  ifactor myprojectile
    setthisprojectile[THISACTOR].cstat 32768
endevent

tried these to make sure they don't work; the projectile is still visible
I'll combine it with event_game and movesprite in a bit to see if it magically erases the first frame.
The default cstat is 0 and the workslike is 32770.

[lllllllllllllll]

EGS to set invisible projectile
GAME to unset invisible projectile
eshoot for movesprite on the projectile

The projectile itself is set to PROJ_VEL_MULT 24

onevent EVENT_GAME
  ifactor myprojectile
  {
    ife var4 1
    {
       setthisprojectile[THISACTOR].cstat 32768
       setav[THISACTOR].var4 0
     }
  }
endevent

onevent EVENT_EGS
  ifactor myprojectile
  {
    setthisprojectile[THISACTOR].cstat 32768
    setav[THISACTOR].var4 1
  }
endevent


//actor code
  {
    eshoot myprojectile
    cos var1 sprite[RETURN].ang
    sin var2 sprite[RETURN].ang
    shiftr var1 3
    shiftr var2 3
    movesprite RETURN var1 var2 0 CLIPMASK0 var3
  }
//

[lllllllllllllll]

In case of event_game running at tick 0 I tried this too

onevent EVENT_GAME
  ifactor myprojectile
  {
    ifl var4 2
    {
      add var4 1
      ife var4 2
      setthisprojectile[THISACTOR].cstat 32768
    }
  }

[Danukem]

Did you try making the projectile's default cstat 32768?

[lllllllllllllll]

Yeah
If it starts with 32768 it's staying invisible
If it starts with 0 it's staying visible

[RichardStorm]

I wonder what's the way to suppress player movement from controller/gamepad, movement_lock only stops player movement from keyboard, indeed, as the wiki states.
I dunno if it's a trick about some player member i'm not aware of, or it's done by manipulating extbits or stuff like that. For sure I saw controller movement is turned off when in-game menus/datapads are on in AA or AMC iirc, but i have no clue on how to search for the solution.

[VGames]

Set the player X y and z velocity to 0

[RichardStorm]

I thought the same solution at the beginning (very simple indeed), but I was not sure about being in a menu while on conveyors etc... then i just veryfied and yes, the player gets totally locked. Going to zero posxv/posyv

[RichardStorm]

Hmmm... Apparently, even if setting posxv and posyv to 0, the player still retains a bit of movement from controller. I tried setting posxv/posyv into APLAYER / EVENT_GAME, then into EVENT_WORLD, EVENT_PREWORLD, and even EVENT_PROCESSINPUT with no positive results (I also tried xvel/yvel but is long known it doesn't work that way). I wonder what i don't know or what am I doing wrong.

[Danukem]

 RichardStorm, on 26 September 2023 - 07:15 AM, said:

Hmmm... Apparently, even if setting posxv and posyv to 0, the player still retains a bit of movement from controller. I tried setting posxv/posyv into APLAYER / EVENT_GAME, then into EVENT_WORLD, EVENT_PREWORLD, and even EVENT_PROCESSINPUT with no positive results (I also tried xvel/yvel but is long known it doesn't work that way). I wonder what i don't know or what am I doing wrong.

Yep, I was going to say something but you guys seemed happy with the solution so I stayed quiet.

The actual solution is to set the fvel and svel members of the input struct to 0 in EVENT_PROCESSINPUT:

https://wiki.eduke32...ructure_members

[RichardStorm]

Now it works properly, many thanks Dan. :pray:

[Mark]

I'm working on a ( polymer ) project with a lot of candles, sconces and flames. I am using the flickering lights code portion of High Treason's CONFETTI mod and its OK. It flickers by randomly changing the radius of the light cast. However, I would like to see how well the flickering effect would work by changing the light's intensity instead of radius. The code would allow me to set the minimum and maximum intensities along with the rate of change.

Is there anyone out here who would like to tackle this request? I could Paypal you some pizza money for the effort.

[Danukem]

Mark, on 05 October 2023 - 07:45 AM, said:

I'm working on a ( polymer ) project with a lot of candles, sconces and flames. I am using the flickering lights code portion of High Treason's CONFETTI mod and its OK. It flickers by randomly changing the radius of the light cast. However, I would like to see how well the flickering effect would work by changing the light's intensity instead of radius. The code would allow me to set the minimum and maximum intensities along with the rate of change.

Is there anyone out here who would like to tackle this request? I could Paypal you some pizza money for the effort.

So what is it that you want changed on the light exactly that isn't the radius? Because IIRC polymer doesn't specifically have an intensity value that is independent of the radius.

[Hendricks266]

Lights use additive blending, so scale your RGB down linearly to achieve a reduction in intensity.

[Mark]

Before trying to figure out how to mess with intensity I decided to try and figure out what was the specific issue I had with my present code. I determined the problem was the randvarvar command was spitting out random numbers for light radius between 0 and the hitag for the sprite. Going so low was giving me too much flicker variation. So I used the addvar command to add a value to whatever comes out of randvarvar so it never approaches 0. After tweaking various parameters for the lights I have close to what I wanted.

I'm guessing curiosity might eventually make me pursue the intensity option ( I'll likely need help with that ) but for now I'll enjoy what I managed to do.

[Danukem]

Yeah for a candle start with a base value then add the random flicker since the flame is never completely out. The alternative method Hendricks266 outlined in that discord post might work well too or better in some ways, probably worth experimenting with.

[Mark]

Can anyone send me in the direction of a previous mod's code that implemented fullscreen title and menu graphics as opposed to the usual square box? If not, is it something easy enough to post here? I haven't done a lot of coding in the last 6 months so my already limited knowledge is rusty. I was dazed and confused looking thru the wiki.

[Danukem]

Mark, on 24 November 2023 - 08:42 PM, said:

Can anyone send me in the direction of a previous mod's code that implemented fullscreen title and menu graphics as opposed to the usual square box? If not, is it something easy enough to post here? I haven't done a lot of coding in the last 6 months so my already limited knowledge is rusty. I was dazed and confused looking thru the wiki.

I'm not sure what you are asking. It sounds like you want widescreen to be the default, but what do you want to happen if the player has a non-widescreen resolution?

[Mark]

I didn't give it much thought. I'm assuming that anyone that might play my style of mod will normally be a widescreen user. Polymer, 3d models, high res graphics. Plus its just the backround screen textures I would want to be fullscreen. The center aligned menu text could remain as-is if thats possible. So if someone were to play in a different res all they would miss is the outer edges of the backround screens. This isn't a must have feature but I thought I would throw it in if it isn't too difficult to implement.

[Danukem]

Mark, on 25 November 2023 - 05:53 AM, said:

I didn't give it much thought. I'm assuming that anyone that might play my style of mod will normally be a widescreen user. Polymer, 3d models, high res graphics. Plus its just the backround screen textures I would want to be fullscreen. The center aligned menu text could remain as-is if thats possible. So if someone were to play in a different res all they would miss is the outer edges of the backround screens. This isn't a must have feature but I thought I would throw it in if it isn't too difficult to implement.

Are the tiles in question already being displayed in your project? I can only guess that you have put them in to replace the tiles in the hardcoded display. Is that correct? If that's the case then what you want to do is cancel the hardcoded display events and use your own screen drawing commands to display your own tiles.

[jimbob]

would it be possible to hack the camera/viewscreen code to use for a small cutscene ( say peeking through a crack like thing so you "see" the other side, and throw the player out at a certain command? ) or would another method be easier, in the end i want it to be triggerable just once, maybe have the player seeing "nah, i've seen enough" or something once its done.

[Danukem]

jimbob, on 27 November 2023 - 02:00 PM, said:

would it be possible to hack the camera/viewscreen code to use for a small cutscene ( say peeking through a crack like thing so you "see" the other side, and throw the player out at a certain command? ) or would another method be easier, in the end i want it to be triggerable just once, maybe have the player seeing "nah, i've seen enough" or something once its done.

Make a tile with a keyhole shape cutout or whatever, then you overlay that on the screen in the display event and set the camera position and angle to where you want it, lock the player in place and set up the trigger for unlocking the player and teleporting them. The good news for you is that several released mods have cutscenes like this and more elaborate ones.

[jimbob]

sounds easy enough, i'll mess around with that, thanks

[December Man]

Hey.

I'm using the following code to have debris and gibs land on the ground and stay there.

state getfloordist
  getactor[THISACTOR].x x
  getactor[THISACTOR].y y
  updatesector x y TEMP7
  getflorzofslope TEMP7 x y z
  getactor[THISACTOR].z TEMP8
  subvarvar z TEMP8
  shiftvarr z 8
  subvar z 1
ends

Unfortunately, each time a gib flies out of map bounds, this line appears in the log:

ERROR| game.con:801: getflorzofslope: invalid sector -1

After an hour of playtime the log might be a couple of megs large due to this and weird stuff starts to happen. How do I fix this?
Thanks in advance.

[Danukem]

Merry Christmas!

state getfloordist
  getactor[THISACTOR].x x
  getactor[THISACTOR].y y
  updatesector x y TEMP7
  ifvare TEMP7 -1 { killit break }
  getflorzofslope TEMP7 x y z
  getactor[THISACTOR].z TEMP8
  subvarvar z TEMP8
  shiftvarr z 8
  subvar z 1
ends

I'm not sure if that fixes it because the issue could be happening further downstream in code that you didn't show. But the concept is simple enough -- do not allow the jibs to persist when out of bounds!

[December Man]

Thanks for the quick reply, it works!

And Merry Christmas!

[Mark]

I'm adding 3d model hub weapons in my polymer mod. I was able to disable the global screen flash when firing weapons but the hud model itself still goes a brighter shade when firing. How would I disable that effect?

I also noticed that after spending a lot of trial and error time getting all the hud offsets the way I wanted, the position shifted when I added the nobob command. I can deal with it but just thought I'd mention it in case others plan to use the nobob. Apply it before you start adjusting position.

[Danukem]

Mark, on 30 December 2023 - 07:48 AM, said:

I'm adding 3d model hub weapons in my polymer mod. I was able to disable the global screen flash when firing weapons but the hud model itself still goes a brighter shade when firing. How would I disable that effect?

I also noticed that after spending a lot of trial and error time getting all the hud offsets the way I wanted, the position shifted when I added the nobob command. I can deal with it but just thought I'd mention it in case others plan to use the nobob. Apply it before you start adjusting position.

You have to be using CON code to display the weapon. If you are just overwriting the hardcoded tiles with your models, then they will inherit the hardcoded display features such as using a bright shade when firing.

If you are already using code for the display, then you just need to find where the shade is being set and make the edit so it doesn't brighten when firing.

[Mark]

Thanks. I guess I can live with it. Its not a huge thing like the global flash was. Coding weapons from scratch is beyong my skills. It was my hope some event could intercept and cancel the shade change.