[Diaz]

Yes and no. I want every enemy model to be lit only by a Polymer light when shooting, instead of getting a shade value.

Some enemies are regular tile numbers, and others are useractors. Behavior seems to be the same.

By the way, setting the shade of the sprite to current sector's floorshade in the actor code doesn't seem to work (I guess the hardcoded shading is applied after my code so it has no effect)

EDIT: Nevermind, setting the shade in EVENT_GAME does work. Marvelous!

[RichardStorm]

Setaspect seems broken. Or this is what i think. I used it some years ago and it worked but now it does nothing. I tried it as with vars as with defined values.

onevent EVENT_DISPLAYREST
....
setvarvar temp ydim  divvar temp  5  mulvar temp 524288
divvarvar temp xdim   
setaspect 32768 temp
// or
setaspect 32768 78644  // being 78644 the right value for 4:3 ... for my 5:4 screen it's 83866 but it doesn't change anything.

endevent
 

What is wrong ?

[rasmus thorup]

I can tell you that setaspect is working because i have been toying with it this past week. Do you have the latest eduke?

[Marcos]

setaspect only works in EVENT_DISPLAYROOMS.

[rasmus thorup]

Oh yea, i thought he was actually in that event. REST and ROOMS -.-

[RichardStorm]

Quote

setaspect only works in EVENT_DISPLAYROOMS

Hell yeah! It works... tks

[Jan Satcitananda]

marcolino123, on 27 March 2012 - 09:31 AM, said:

setaspect only works in EVENT_DISPLAYROOMS.

This command is useful in other display events as well if you want to stretch things shown via rotatesprite and similar commands. For instance, setaspect 32768 65536 removes the unwanted vertical stretching what is crucial for proper rotation.

[Danukem]

CraigFatman, on 28 March 2012 - 07:21 PM, said:

This command is useful in other display events as well if you want to stretch things shown via rotatesprite and similar commands. For instance, setaspect 32768 65536 removes the unwanted vertical stretching what is crucial for proper rotation.

That's good to know. I HATE that vertical stretching; it has ruined so many graphics for me. But does that work in all renderers?

[Superthijs]

How do I unblock a sprite in code?

[Mblackwell]

http://wiki.eduke32.com/wiki/Cstat

eg:
cstat 0
or
setactor[THISACTOR].cstat 0

[Superthijs]

Yeah, I know, sorry, I should have explained a little bit more.
I actually mean that, if the cstat is 14, 52 or 25, or something like that, I want to subtract 1 of the cstat.
So I need to check if the sprite is blocked or not.

[Helixhorned]

andvar X 0xFFFFFFFE

This is proposed by CraigFatman, but I find the "obvious" version easier to read (and unlikely to be different performance-wide unless used in a tight loop):

ifandvar X 1
   subvar X 1

[Hendricks266]

Helixhorned, on 03 April 2012 - 05:10 AM, said:

andvar X 0xFFFFFFFE

This is proposed by CraigFatman, but I find the "obvious" version easier to read (and unlikely to be different performance-wide unless used in a tight loop):

ifandvar X 1
   subvar X 1

DT suggested:

ifandvar X 1
   xorvar X 1

It would be easier if we had nandvar, I think.

[Diaz]

Superthijs, on 03 April 2012 - 05:00 AM, said:

Yeah, I know, sorry, I should have explained a little bit more.
I actually mean that, if the cstat is 14, 52 or 25, or something like that, I want to subtract 1 of the cstat.
So I need to check if the sprite is blocked or not.

Use getactor[THISACTOR].cstat CSTAT to get the cstat into a variable called CSTAT. Then you can check if it's already blocking or not by using ifvaror CSTAT 1.
If not, just add 1 to the variable and use setactor[THISACTOR].cstat CSTAT to set the updated value.

[rasmus thorup]

It's ifvarand if i remember correctly.

[Diaz]

Hmmm... I use ifvaror on some parts of my code and it seems to work..

[rasmus thorup]

I always forget what those, and, xor things does. Would be nice if someone could write something on the wiki, the wiki isn't very helpful right now. But ifvarand works for me when i check if a bit number is on.

[Superthijs]

Thank you guys!

[Superthijs]

I have another question: Doesn't 'ifcount' work inside an event?
I'm using this code to simulate jetpack flames, but it doesn't wait between the spawning of the flames.
After half a second, the game crashes showing the 'too many sprites spawned' message.

onevent EVENT_GAME
    ifp pjetpack
    {
        ifcount 2
        {
            espawn EXPLOSION2
            setactor[RETURN].xrepeat 16
            setactor[RETURN].yrepeat 16
            resetcount
        }
    }
endevent

I have the feeling I'm doing something wrong.
Any ideas?

[Diaz]

ifcount is an actor counter. That code should go inside the APLAYER actor code instead of EVENT_GAME.

[rasmus thorup]

You can also put a ifactor APLAYER command so only the APLAYER will spawn it. Though i am not sure if this will work because of the count thing. But i want to know

[Superthijs]

Thanks!

[Superthijs]

Sorry, I'm just overloaded with questions...
How do I make an actor shoot a projectile with another vertical angle? I've managed to make it shoot towards where the player is looking at,
but it keeps shooting at the same vertical angle. Even when the player looks up or down.

[Hendricks266]

zshoot

[Mblackwell]

Superthijs, on 12 April 2012 - 09:00 AM, said:

Sorry, I'm just overloaded with questions...
How do I make an actor shoot a projectile with another vertical angle? I've managed to make it shoot towards where the player is looking at,
but it keeps shooting at the same vertical angle. Even when the player looks up or down.

In addition to what Hendricks said, if you know your target:

http://wiki.eduke32....or_aim_vertical

[Superthijs]

I don't have a specific target, I just want it to shoot freely.

[Superthijs]

So how do I get the player's vertical angle, just like a sector slope (e.g. 4096)?

[rasmus thorup]

Do you mean this? http://wiki.eduke32.com/wiki/Horiz
Someone messed up.

[sedition]

Is there a special editor for EDuke-Scripting? I´m working with Notepad++, but I was wondering if there´s a special one which works better with Con-Scripting.

[rasmus thorup]

No. that's what most of us use.