[m210®]

I have problems with activating SE12 via CON commands.
operateactivators, operatemasterswitches, operaterespawns, operatesectors, activatebysector doesn't works for it. How to do this?

[CruX]

M210, on 02 March 2012 - 04:43 AM, said:

operateactivators, operatemasterswitches, operaterespawns, operatesectors, activatebysector doesn't works for it. How to do this?

Yeah, none of those commands will work because the lightswitch doesn't work with activators or sector tags (etc.) it all happens within the SE. That being said, you'd have to find some way to alter the SE to make it jive with checkactivatormotion or something like that. I don't mess around with SE's or really any of those actors so I can't help with that. If I were you, I'd just make a new actor that uses checkactivatormotion, then changes the floorshade of the sector it's in to a certain parameter defined in its hitag (or some other struct member like that) if the activator in motion equals a certain other struct member (lotag, extra, etc.)

And as long as I'm mentioning checkactivatormotion, is there some other sort of command I'm not aware of that checks the motion of a sector itself? I created an actor some time ago that would play two different, specific sounds for when a door opened and closed (like in Doom), but ATM it's using checkactivatormotion to keep tabs of when the door's actually opening and when it's closing, ergo every door that uses this actor HAS to be operated by a switch. I'd kind of like for it to also work with regular doors that you can open with the spacebar, but I can't find any command or check that would help with that.

[m210®]

It's sadly that no way to make it, but anyway thanks. Probably have to make a sprite myself, although I don't want to do this

[m210®]

And a second question, is there way to check ceilings on hits of radiusexplosion by projectiles?
that's very easy to get via bullets like this

getactor[THISACTOR].picnum picnum
ifvare picnum SHOTSPARK1 
{ 
	getactor[THISACTOR].htg_t 6 tmp
	ifvare tmp -1
	{
		getactor[THISACTOR].htg_t 7 sectorid
		getactor[THISACTOR].z sector_z1
		getsector[sectorid].ceilingz sector_z2
		ifvarvare sector_z2 sector_z1 {        }
	}
}

but I can't to make such code for projectiles...
because projectiles can damage ceilings even if it get into the wall

[m210®]

Ok, I made own LightEffector. The result is a very good tool. For example now I can highlight walls and floor only. And I made a new video with some effects on E1M2 from BloodTC.

And about mapster32 scripts. I got a one idea when I saw savegamevar
Maybe make those command for mapster32? Save a variable and value to file in m32 than call variable in the game?

[Diaz]

Is operateactivators currently broken?

I've made an actor that is supposed to trigger activators whose lotag match the actor's hitag when it's killed (it's a monster). The code works fine bacause it prints out the debugging quote I've added, but it's not triggering the activators. Even if I set it to operate activators defined by a fixed number (just in case I'm not parsing the hitag correctly), it won't work.

    getplayer[THISACTOR].i TEMP
    checkactivatormotion HITAG
        ifvarn RETURN 1
        {
            quote 100
            operateactivators HITAG TEMP 
        }

This code is executed on the ifdead... section of the actor's ifhitweapon code.

[Danukem]

Try using 0 instead of TEMP. You are putting the player sprite's ID number in there, but what you actually want is the player number, which is 0 in a single player game. In general, it never hurts to use 0 for that parameter in my experience.

[Diaz]

That worked, thanks! I thought that parameter was just related to the "locked" or "unlocked" quotes and wasn't very important, but looks like it is...

[Danukem]

Diaz, on 12 March 2012 - 08:55 AM, said:

That worked, thanks! I thought that parameter was just related to the "locked" or "unlocked" quotes and wasn't very important, but looks like it is...

Well it's important insofar as players that don't exist can't activate shit.

[Diaz]

well yeah lol... I just thought that parameter wasn't about who activates stuff, but just who gets to see the quote

[Simon_Croes]

When I draw a fullscreen (320x240 in 8-bit) image on the screen it is in 4:3 format and not widescreen, because I want it to stretch over the screen. I could be wrong but I thought that they used widescreen in AMC TC to draw the screens, that worked. Turning widescreen on in the video options doesn't help. Is this some kind of script or con code?

Thanks for helping me out

[Mblackwell]

Let me explain a bit:

320x240 = 4:3

Duke actually uses 320x200 which is 16:10. Then it does some weird crap and stretches that to fit in various 4:3 resolutions.

So first start there, make your graphic the correct 320x200 resolution and that will "fill the screen" on a 4:3 res. Then in rotatesprite (or myospal or whatever) set your orientation to 1024. Note that this will distort the image, but it WILL cover the screen.

Setting widescreen has no effect on graphics that weren't displayed with orientation 1024 set.

[Simon_Croes]

Ah thanks a lot Mblackwell. And yeah, I wasn't sure if my picture was 320x240 or 320x200. I just wanted it to stretch over the screen Thanks again for the help, work perfectly now!

[Diaz]

A quickie:

Is it possible to make it so enemies (hardcoded and useractor enemy) do NOT light themselves up when firing projectiles?

Right now I'm making them notenemy but ofcourse there are some drawbacks, like autoaim not working on them...

[Mblackwell]

Diaz, on 25 March 2012 - 04:46 AM, said:

A quickie:

Is it possible to make it so enemies (hardcoded and useractor enemy) do NOT light themselves up when firing projectiles?

Right now I'm making them notenemy but ofcourse there are some drawbacks, like autoaim not working on them...

For the polymer lights Htflags should theoretically do it.

Also... I'm not sure how not being able to autoaim at enemies is a drawback

[Jblade]

I think he means how to make the enemies not light up as in shade 0, not polymer lights - I *think* it might be worth trying getting the sector's shade and applying it constantly whilst the enemy is shooting, but I'm not that sure.

[Mblackwell]

James, on 25 March 2012 - 06:35 AM, said:

I think he means how to make the enemies not light up as in shade 0, not polymer lights - I *think* it might be worth trying getting the sector's shade and applying it constantly whilst the enemy is shooting, but I'm not that sure.

Shooting a projectile doesn't light anything up though (at least if it's notenemy). The exception to this is polymer, because things like SHOTSPARK1 are coded to cause a light to spawn.

[Jblade]

Mblackwell, on 25 March 2012 - 06:45 AM, said:

Shooting a projectile doesn't light anything up though (at least if it's notenemy). The exception to this is polymer, because things like SHOTSPARK1 are coded to cause a light to spawn.

Yeah an enemy actor does become fullbright if they're firing a shotspark weapon, I thought that was what he meant.

[Plagman]

Right, he just said notenemy fixed it.. He wants the shade to remain constant for enemies.

[Mblackwell]

Plagman, on 25 March 2012 - 06:53 AM, said:

Right, he just said notenemy fixed it.. He wants the shade to remain constant for enemies.

Setting the shade manually would be the only way to do it then afaik.

[Diaz]

Yeah, that's what I was talking about. So it's the shade value that needs to change? I'll see if I can get it manually adjusted...

[Danukem]

Diaz, on 25 March 2012 - 07:25 AM, said:

Yeah, that's what I was talking about. So it's the shade value that needs to change? I'll see if I can get it manually adjusted...

Are these enemies you are having the problem with on the regular enemy tile numbers (like PIGCOP, LIZMAN, etc.)?

[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?