[Danukem]

You could try this approach:

getactor[THISACTOR].ang angvar

ifhitweapon
{
	setactor[THISACTOR].ang angvar

But that won't work unless the angle changes when ifhitweapon is checked. A foolproof method is to have the actor save their angle each tic at the end of their code, then restore to the saved angle when ifhitweapon is true

[XThX2]

Yes, thanks for that ! They indeed change their angle when ifhitweapon is true. The foolproof method you suggested works perfectly.

[Fox]

I can only see an model if I am facing the basic actor. How can I make sure I will always see it no mather where I am?

[Fox]

I am trying to add an continuous black screen from when an gameend (startlevel command) and it starts. But there is an delay in displayrest which it for an instant it doesn't show anything.

Any idea so that I can make it has no blank spot?

[XThX2]

		  getactor[THISACTOR].z z2
		  getplayer[THISACTOR].i ID
		  getactor[ID].z posz
		  subvar z2 8192
		  subvarvar z2 posz
		  ldist xyvalue2 THISACTOR ID
		  mulvarvar z2 z2 mulvarvar xyvalue2 xyvalue2
		  addvarvar z2 xyvalue2
		  sqrt z2 z2
			ezshoot z2 YELLOWROCKET
/*			getactor[THISACTOR].x x
			getactor[THISACTOR].y y
			getactor[THISACTOR].ang TEMP
			setvarvar y2 y
			addvar y2 128
			rotatepoint x y x y2 TEMP x3 y3
			setactor[RETURN].y y3 */

I was trying to make an actor shoot another from some distance with accurate vertical aim. The enemy targets player, and has rocket launcher mounted on his back, so he fires from a bit higher than the actor's Z. I thought of the case, draw some simple sketches and found out that phythagoras would just work fine. Difference between Z's form the height, their distance forms the base, and finally, the result forms the zvel it must come from. So, where have I been mistaken with this idea ? D:

[EDIT] : Forgot to say what doesn't work. The actor shoots at his feet if player is too far, and even behind himself which can actually go really far. If player is really close, then the rocket goes where it is supposed to, but most of the time, missed the player.

[TerminX]

Z coordinates aren't the same scale as X/Y coordinates...

[Danukem]

What TerminX said. Also, I don't understand why you are changing the y coordinate of the projectile.

[XThX2]

I worked that one out. I have a harder issue now that I can't seem to solve. I've been messing around with this for 4 days.

  ifai AIHTROTELEPORT
  {
	  ifvarand status 4 nullop else { ifvare temprand 0 setvar temprand -1 addvar status 4 }
	  
	  whilevarn spritenum 16384
	  {
		  getactor[spritenum].picnum picnum
		  ifvare picnum EFFECTSPRITE
		  {
			  getactor[spritenum].lotag lotag2	
			  getactor[spritenum].hitag hitag2
			  whilevarn arrayholder 128
			  {
				  setarray container[arrayholder] lotag2
				  setvarvar arraycheck container[arrayholder]
				  setarray container[arrayholder] hitag2
				  setvarvar arraycheck2 container[arrayholder]
				  
				  ifvarvarn temprand randomvar5 ifvarvare randomvar5 arraycheck ifvarvare arraycheck2 yvel2
				  {
					  getactor[THISACTOR].x mx
					  getactor[THISACTOR].y my
					  getactor[THISACTOR].z mz
					  getactor[spritenum].x x2
					  getactor[spritenum].y y2
					  getactor[spritenum].z z2
					  getactor[spritenum].sectnum mysector
					  sound TELEPORTER
					  espawn TRANSPORTERBEAM
					  setactor[RETURN].x mx
					  setactor[RETURN].y my	  
					  setactor[THISACTOR].x x2
					  setactor[THISACTOR].y y2
					  ifvarn mysector -1 setactor[THISACTOR].sectnum mysector
					  subvar z2 1024
					  setactor[THISACTOR].z z2
					  sound TELEPORTER
					  espawn TRANSPORTERBEAM
					  setactor[RETURN].x x2
					  setactor[RETURN].y y2
					  setvarvar temprand randomvar5
					  ai AIHTROSHOOT1
				  }
				  addvar arrayholder 1
			  }
		  }
		  addvar spritenum 1
	  }
  }

I wanted my guy to teleport to one of the "hitag" amount of teleporters which it's yvel also checks. I place hitag amounts of these "dummy actors" to where I Want this guy to teleport, and give them lotags starting from 0 to hitag. This guy randomly picks one of them, and teleports to the corresponding lotag of the randomed number. The problem is, it only teleports to a fixed place, which is only 1.

I thought of the general issue first, and thought that it was the tags of effectors not being set, and only the last one. So, I decided to use arrays and increase each array by 1, so that it would check it; in a secondary while loop. I'm not sure if I'm overcomplicating things, or missing something so little again; but this is basically the first time I touched arrays :/ (The idea is like in Heretic's D'sparil fight, the wizard randomly teleports to one of the 4 fixed places)

[Danukem]

Ok, I've only read the first few lines, but already I see that you did not set spritenum to 0 before starting the loop. Or if you did set it, you didn't show that part of the code.

[XThX2]

Oh yeah I forgot that part, but it is set before that AI is initiated along with some other variables. Here's that line.

ifspritepal 0 { ifrnd 72 { ai AIHTROPAIN sound HTRO_PAIN } } else { ifrnd 64 { ai AIHTROPAIN sound HTRO_PAIN } else { setvar randomvar5 0 setvar arrayholder 0 setvar arrayholder2 0 randvarvar randomvar5 yvel2 setvar spritenum 0 ai AIHTROTELEPORT } }

[Danukem]

Ok, I've read a few more lines of the code now.

The normal procedure when dealing with sprites that aren't SEs or the other hardcoded effect actors, is to get their lotags and hitags into variables at map load time using the eventloadactor command. Then you set their lotag and hitag struct members to 0 to prevent nasty hardcoded effects and refer only to the variables from that point forward. In your code you are checking the struct members, not the variables. Are you sure that isn't a problem?

[NF64]

If I wanted to change the camera angle would that be found in the game.con or hard coded? Because I couldnt find it in the game.con.

[Danukem]

Nfelli64, on Sep 19 2009, 07:06 PM, said:

If I wanted to change the camera angle would that be found in the game.con or hard coded? Because I couldnt find it in the game.con.

Look at this and read the note at the top that I just edited:

http://wiki.eduke32.com/wiki/Confaq42

To reposition the camera, you will need to change the values of the camera variables (e.g. cameraang) in a display event. You will have to learn a lot of stuff before you can do that competently.

[NF64]

Quote

To reposition the camera, you will need to change the values of the camera variables (e.g. cameraang) in a display event. You will have to learn a lot of stuff before you can do that competently.

simple enough.

[Fox]

I am trying to create beetween levels animations, intermission screens, etc. Although whenever I play a sound it is affected by game environment, this is, being underwater or after defeating a boss (command endofgame 52) which stop the sound from playing.

Any idea?

[Danukem]

You could make a little sector somewhere and teleport the player to it.

[Fox]

Setting sector lotag to 0 and timebeforeexit to 0 does the work perfectly.

[XThX2]

I'm sure I've asked this in the past but I ask it again hoping I'll have a clue this time. I have been trying to code the "bullets going thru if dead" for shotgun/supershotgun for my mod and I have a rather crappy way of doing it; which is by small delays. (Shooting 6 pellets per frame of the weapon up to 4 frames which makes 24 pellets) and... well it works the way it is supposed to be, however it is not really satisfying. First, you can spread the pellets wider by looking left/right/up/down. Also, there will only be 6 pellets going through if it happens.

I was playing the game and found out that some actors have this property such as CHAIR1, CHAIR2, vases, and even the slimer. When you shoot them, the pellets go through them when one hits them. I checked the source code for such things but couldn't find; so what I'm asking is if anyone can provide me information about how this can be done, or is done in the game ? (I'm hoping that it's not hard-coded for the first pellet hitting the object, then the rest going through)

[Danukem]

XThX2, on Sep 26 2009, 02:06 PM, said:

(I'm hoping that it's not hard-coded for the first pellet hitting the object, then the rest going through)

Well of course it is hardcoded. Otherwise it would be possible to add to any actor using 1.5 CON commands.

[XThX2]

I meant, coded to act that way. If so, it would be really useless to add on enemies.

[Fox]

Yeah, it would be good if there was an spriteflag or something for that.

[Mblackwell]

Why not just have the actor that was hit calculate the angle the bullet that hit it was shooting from and shoot a second bullet?

[Danukem]

Mblackwell, on Sep 26 2009, 08:08 PM, said:

Why not just have the actor that was hit calculate the angle the bullet that hit it was shooting from and shoot a second bullet?

That's better than nothing, but it's not great.

The second bullet will have a random component to its angle, because there is still no way to modify ANGRANGE when fired from a non-player. Also, it would be hard to recover the vertical angle accurately. And what if the actor got hit by more than one bullet at the same time? There's no way to know that just from checking the actor. Plus, you don't even know where the bullet hit, and when the actor fires the new bullet it will shoot from its mid-section regardless.

A better source of information is the SHOTSPARK1 actor itself, when it spawns. You get the exact location that it hit, the angle it is facing, and by comparing its location relative to the player you can recover the vertical angle as well. Plus there is one such actor for each bullet, so there's no problem in knowing how many hit. But deciding whether the SHOTSPARK1 should fire a new bullet, and then doing so with the right results presents its own problems.

[Fox]

Is it possible to get in a gamevar what is the width and height in pixels of an specific tile number? For example, for making a background.

I suppose it is possible, as it seems to affect gameplay (for example a blocking wall sprite, etc).

[XThX2]

DeeperThought, on Sep 26 2009, 11:47 PM, said:

That's better than nothing, but it's not great.

The second bullet will have a random component to its angle, because there is still no way to modify ANGRANGE when fired from a non-player. Also, it would be hard to recover the vertical angle accurately. And what if the actor got hit by more than one bullet at the same time? There's no way to know that just from checking the actor. Plus, you don't even know where the bullet hit, and when the actor fires the new bullet it will shoot from its mid-section regardless.

A better source of information is the SHOTSPARK1 actor itself, when it spawns. You get the exact location that it hit, the angle it is facing, and by comparing its location relative to the player you can recover the vertical angle as well. Plus there is one such actor for each bullet, so there's no problem in knowing how many hit. But deciding whether the SHOTSPARK1 should fire a new bullet, and then doing so with the right results presents its own problems.

I thought it would be a lot of work to do as well, which would have bugs. Right now, there's nothing I can do but to find the way to provide the smallest delay of all. For one thing, I've tried ifvarn and it's not really fast. I also tried the htg_t of the actor, still not enough. I tried whilevarn at some point but it was too fast that they were being fired at the same time.

So, what can I do to provide an almost unnoticable delay between all 24 shots ? (Or per 4 shots for 6 tries, 3 for 8 and such)

[Fox]

You can't. A tick is 1/26 of a second. That nothing fast.


I am not sure how you could do it, but I have discovered something close to that.



There you can see the shots are at different angles. During EVENT_EGS I use SHOTSPARK1 to change the player angle. And the delay equal to zero.

===//===//===

What is the best way to simulate a multiplayer game? I heard you can do it through the console command, but I don't know how. =/

[Mblackwell]

Code executed in actor loops occurs each tic, code executed in EVENT_EGS I believe occurs each tic for each actor (EG: 1K actors = 1K times per tic), code executed in a Display event (EVENT_DISPLAYREST, etc) occurs once per frame rather than per tic.

[Danukem]

Mblackwell, on Sep 27 2009, 08:23 AM, said:

Code executed in actor loops occurs each tic, code executed in EVENT_EGS I believe occurs each tic for each actor (EG: 1K actors = 1K times per tic), code executed in a Display event (EVENT_DISPLAYREST, etc) occurs once per frame rather than per tic.

EVENT_EGS code is executed immediately when something is spawned and then never again for that sprite. For example, in "espawn PIGCOP setactor[RETURN].pal 17" the EGS code runs right after the spawn and before the pal is set. Maybe you were thinking of EVENT_GAME?

[Mblackwell]

DeeperThought, on Sep 27 2009, 11:06 AM, said:

EVENT_EGS code is executed immediately when something is spawned and then never again for that sprite. For example, in "espawn PIGCOP setactor[RETURN].pal 17" the EGS code runs right after the spawn and before the pal is set. Maybe you were thinking of EVENT_GAME?

Yes.

[Chip]

Right then, how would I go about making an actor of mine become (or make) a light source?
In the old Polymer thread started by DT, he said that he had actors spawn SECTOREFFECTORS and the actors controlled them.
I've just tried that but the very instant a SECTOREFFECTOR is spawned (or espawned) the game crashes with -found lonely sectoreffector at x y ..... So I had it spawn a dummy actor first, set its values then change its picnum to a SECTOREFFECTOR but then the game would er.. no crash but not work either. The game would "pause" all map present actors of all types except the player allowing me to wounder around a map in a photo like mode - taking screen shots of current scenes and events from different angles!
However any newly spawned actors would work as normal

It was interesting but not what I wanted.
Basically how would I have my own non hard coded light sources in game? I intend to have things like flame throwers, weapons and such which need to spawn a light source so I can't just hide them off map and move them into place.