[Hendricks266]

D'oh! That's what I get for doing this from memory.

gamevar screenx 0 0
gamevar screeny 0 0

defstate menuwhatever
    getuserdef .m_origin_x screenx
    getuserdef .m_origin_y screeny

    ifvare RETURN 110 // MENU_SKILL
    {
        // use screentext with the <<16 bit set, and *add* the coordinates you want to draw to screenx/y so it animates with the menu
    }
ends

onevent EVENT_DISPLAYMENUREST
    state menuwhatever
endevent

onevent EVENT_DISPLAYINACTIVEMENUREST
    state menuwhatever
endevent

[Danukem]

Is there a way to force a sprite to be rendered, even if it is behind a wall? I seem to remember someone saying so, but I don't recall how. Setting the sprite's sector to the same as the player's does not do it.

[Fox]

You can just put it closer to the player view, then simulate the distance with the sprite scale, but it would lack precision.

[Jblade]

Would setting it's animatesprite x and y values work? You could have the sprite close to the player but change it's tsprite values so it's displayed where it should actually be in the level.

[Fox]

Nope, animatesprites doesn't work with sprites that are not being rendered.

[Danukem]

Fox, on 18 March 2016 - 03:43 PM, said:

You can just put it closer to the player view, then simulate the distance with the sprite scale, but it would lack precision.

Most of the sprites in question are pickable objects, such as ammo. Doing what you suggest would cause the player to pick them up in some cases. What I'm going for is a kind of X-ray vision that reveals objects in secret areas. But it's okay, I've decided I don't really need it, I can make do with something else.

[Jblade]

Fox, on 18 March 2016 - 06:06 PM, said:

Nope, animatesprites doesn't work with sprites that are not being rendered.

That's why I said move the sprite next to the player like you suggested but keep it's tspr x and y values at its original location. Anyways what I suggested is not what Dan was looking for, the ability to do that would be insanely useful though.

[Fox]

My bad. That would not work, moving it through the tsprite structure would have the same result as being in the original location, except that it would waste some memory processing a sprite that's not visible.

[December Man]

Hey guys. I have two problems.

1. I already created casings that drop on the ground. However, I would like the casings to be visible in first person as they leave the weapon (like the original sprite ones). I know I can modify the angle horizontally that they appear as such, but then the casings drop in front of Duke instead of next to him. I use code such as this:

 ifactor RIFLESHELL
{
move FORWARD
getactor[THISACTOR].ang TEMP
subvar TEMP -412
randvar TEMP2 128
addvarvar TEMP TEMP2
setactor[THISACTOR].ang TEMP
}

I know the fix is probably easy and I'm missing something obvious, but do help a brother out here.

2. Is it possible for the Eggs and Sharks to be counted in the overall tally count BEFORE killing them? (as in, the mid level enemy count that can be turned on in eDuke can show the proper number of enemies instead of an estimate)

[Jblade]

The best thing to do is to use rotatepoint at the time of spawning it and telling the actor to spawn a little bit to the diagonal right of Duke when firing. I have some ugly code here I've used in the AMC TC:

	move FORWARD
	getactor[THISACTOR].ang TEMP
	subvar TEMP -412
	randvar TEMP2 128
	addvarvar TEMP TEMP2
	setactor[THISACTOR].ang TEMP
	getactor[THISACTOR].owner TEMP8
		setvarvar TEMP3 sprite[TEMP8].x
		addvar TEMP3 256
		getactor[TEMP8].ang TEMP4
                addvar TEMP4 128
		rotatepoint sprite[TEMP8].x sprite[TEMP8].y TEMP3 sprite[TEMP8].y TEMP4 TEMP5 TEMP6
		setactor[THISACTOR].x TEMP5 
		setactor[THISACTOR].y TEMP6
		getactor[TEMP8].z TEMP
		subvar TEMP 8096
		ifspawnedby APLAYER
			{
			getplayer[THISACTOR].horiz TEMP2
			subvar TEMP2 100
			mulvar TEMP2 16
			subvarvar TEMP TEMP2
			}
		setactor[THISACTOR].z TEMP

Hopefully you can get a gist of what needs doing. I'm sure the code could be improved but I have a dozen other things that need working on at the same time.

[December Man]

Thanks for the help!

[Mr. Alias Nameless]

Mr. Alias Nameless, on 21 February 2016 - 06:35 AM, said:

Hello everybody. I need a guru. I need to be able to select objects on the screen with the mouse.
I need a function that takes parameters: camerax,cameray,cameraz,camerasect,camerahoriz,cameraang, screenx,screeny (xd,yd) and return x,y,z in build coordinates.

Can somebody help with programming such functions for non classic modes?

I did it!

[Mblackwell]

But does it work in other aspect ratios?

[Mr. Alias Nameless]

Mblackwell, on 12 August 2016 - 12:46 PM, said:

But does it work in other aspect ratios?

What do you mean? Screen resolution - yes to all. Aspect setted up by setaspect function - halfway, it is necessary to choose the coefficients for each values of "viewingrange" and "yxaspect". Now I try to find a mathematical relationship.

[stumppy84]

A quick noob question, I'm trying to code a force-field for the trooper. it works but I cant get the TRANSPORTERSTAR to pallet to 7.. I have tried adding 'spritepal 7' before and after the TRANSPORTERSTAR but neither work..

below the ifwasweapon SHOTSPARK1:

	
sound SOMETHINGHITFORCE
spawn TRANSPORTERSTAR spritepal 7 

[Hendricks266]

Commands like spritepal work only on the current sprite.

espawn TRANSPORTERSTAR
setactor[RETURN].pal 7

[stumppy84]

Thanks again Hendricks!!

[stumppy84]

How hard is it to code in a shotgun knockback feature? That would knock back the actors. I've looked at other mods but it seems a bit complicated...

[Jblade]

A simple way to do it would be like this:

ifvarg sprite[THISACTOR].htextra 0 // Is this actor taking damage?
 {
 getactor[THISACTOR].htpicnum TEMP // get the tile number of the attack
  ifvare TEMP SHOTGUN // if it's the shotgun...
   {
   setactor[THISACTOR].xvel -10 // set its backwards velocity by 10
   }
 }

Make sure to define the TEMP gamevar if you haven't already.

That should do it - it's a quick and dirty method but it should work. Then you can go from there and make it a bit more complex. You would put this in the actor code - I can't remember if it has to be before or after a 'ifhitweapon' statement so try both.

[Mblackwell]

Mr. Alias Nameless, on 15 August 2016 - 11:42 PM, said:

What do you mean? Screen resolution - yes to all. Aspect setted up by setaspect function - halfway, it is necessary to choose the coefficients for each values of "viewingrange" and "yxaspect". Now I try to find a mathematical relationship.

I mean screen resolution, yes. For example setting 16:10 vs 16:9 and 4:3 as well as 5:4

[Micky C]

Mblackwell, on 19 August 2016 - 07:25 AM, said:

I mean screen resolution, yes. For example setting 16:10 vs 16:9 and 4:3 as well as 5:4

Hasn't someone already done code for something like this that works in the software renderer, but is off in the gl renderers due to the different perspective?

It was for drawing boxes around actors from memory.

[Mblackwell]

Yeah I remember that code, but I can't remember what mod that was for.

[stumppy84]

Jblade, on 19 August 2016 - 03:27 AM, said:

A simple way to do it would be like this:

ifvarg sprite[THISACTOR].htextra 0 // Is this actor taking damage?
 {
 getactor[THISACTOR].htpicnum TEMP // get the tile number of the attack
  ifvare TEMP SHOTGUN // if it's the shotgun...
   {
   setactor[THISACTOR].xvel -10 // set its backwards velocity by 10
   }
 }

Make sure to define the TEMP gamevar if you haven't already.

That should do it - it's a quick and dirty method but it should work. Then you can go from there and make it a bit more complex. You would put this in the actor code - I can't remember if it has to be before or after a 'ifhitweapon' statement so try both.

Thanks Jblade! I'm not 100% about defining the 'TEMP gamevar' but I will try to look around the Wiki a bit and see if its explained there..

[Jblade]

gamevar TEMP 0 0 - basically the first letter is the variable's starting number, and the second defines what kind of variable. 0 is global, so everything can access it - 1 is per-player which means it's unique for every player and 2 is per-actor which means it's unique for every single actor

[stumppy84]

Thanks! I couldn't really find in the wiki so this is a great help!!

[Danukem]

stumppy84, on 20 August 2016 - 07:44 AM, said:

Thanks! I couldn't really find in the wiki so this is a great help!!

http://wiki.eduke32.com/wiki/Scripting

You can read the first section on gamevars.

Also, there is an entry here:

http://wiki.eduke32....ar_manipulation

[RichardStorm]

Two bugs found? (using last eduke version, since dunno):

- getting htextra from enemies always returns -1 rather than incurring damage (i also used useractor as additional caution as wiki suggests)

- if adding cstat 256 to dead corpses for being able to shoot them, they use some hardcoded clipping rectangle as high as the living actor (see pic below); maybe i miss something, but I found no way to change it by working on clipdist or various flags.

I know that the first issue can be avoided by constantly checking actor's extra, and the second with separate actors for corpses.
Unfortunately the separate actor solution opens several issues in a project i'm working on, if not solvable via attributes or some strange trick.

Attached thumbnail(s)

• 

[Danukem]

RichardStorm, on 23 August 2016 - 04:05 AM, said:

- getting htextra from enemies always returns -1 rather than incurring damage (i also used useractor as additional caution as wiki suggests)

If that were true it would break just about every one of my mods, and since I have released tested versions of some mods using the latest r5811 snapshot, I have to conclude that you are doing something wrong. Most likely, you are checking htextra after the actor has called ifhitweapon (that command resets htextra to -1).

EDIT: I made an edit to the wiki page to clear that up http://wiki.eduke32.com/wiki/Htextra

[Hendricks266]

The idea behind EVENT_PREGAME and EVENT_PREWORLD is to let you get the htextra before any ifhitweapon commands are run. I don't recall if they actually work for that though.

[RichardStorm]

If only the obscure ifhitweapon behavior was on Wiki ages ago, i'd have skipped that question and not played the "dumb"role. Seriously, why and how do you suppose i had that info ?
Anyway, getting htextra at very top of enemy codes (before states etc) works quite well, many thanks.

But still:

Eduke Wiki of Secrets said:

If the actor in question is a useractor enemy, it will not count damage higher than the actor health.

i get the full amount of damage instead, like getting 200+ when shooting a 30hp liztroop with an rpg. What Wiki i miss, again ?


Now, my main interest is that clipping shaping, i should expect another CON secret...