15 replies to this topic

[Martin Thompson]

Hey, just a question about the func_door_rotating.

In the description, it lists that you can check the TOGGLE spawnflag
for it to be able to be togaalable by a func_usable or such. The spawnflag
however isnt availalbe. How can i get a toggalable func_door_rotating?

BTW, I'm making this map for RPG-X 8.1, so i cant use any of the RPG-X EF entities. I might just have the wrong hmentities.def for my GTK.

GSI, maybe you know which is the correct .def file for 8.1? (The last rpg-x version to work with Vanilla, ioEF and ioCow)

[Harry Young]

Yeah, the def is incorrect. To have it move on toggle set 'wait' to '-1'. Else it is just like another door toggled by target --> targetname relationship

[GSIO01]

Yes Harry is right. wait with value -1 will result in toggleable doors.

[Martin Thompson]

Alright, thanks, I suspected it already from stuff i read around the forums but i wasnt really sure if that was true for rotating doors.
So i just set wait to -1 and target it with a trigger_usable?

[Harry Young]

Well... trigger_usable migth be a bad Idea ^^ but yes, that is the way to go.

[Martin Thompson]

alright, thats working now, but i got another problem, some screenshots might make that clear:




A portal surface is applied with a camera. It works, but only if i look at it from wierd angles. Any ideas?

I already know how to "fix" this with a "hack" but id rather not use more entities then i need.

[Harry Young]

Yeah, I had that as well. It depends on the Position of misc_portal_surface to the Portal-surface and the Camera-direction. I suggest you try around a bit with that.

On the other hand I'd be interested in that fix of yours.

[Martin Thompson]

The fix is really dirty basically, i had this in mind:

In stead of the face of the brush that has the portal, put a black texture in. Then take
a patch and place it where the face of the brush is when the screen is
"out". Then when triggering the screen, trigger the patch as a function usable
after the screen has rotated. Ofc youd need to have a portal texture with the
decall keyword in the shader so you dont get z-fighting with the patch that has the portal on it.

[Harry Young]

ah, okay, I understand that.

[Martin Thompson]

BTW, why would func_usable be a bad idea? Is there somethign better?

[Harry Young]

Take another close look at what you wrote and you'll understant the joke ^^

[Martin Thompson]

Ah yeah lol, my bad

[Martin Thompson]

Alright so yeah, partial got that working now.

I want to extend the system to handle multiple cams.
Now, in the description of the misc_portal_portal it says:

targetname - When used, cycles to the next misc_portal_camera it's targeted

Now, 2 questions:

1: Do all the misc_portal_camera that are targeted need to have the same name (for instance 2 misc_portal_camera with the targetname Cam) or do i need to use target, target2, target 3 etc.

2: When i use the entity, the screens start flickering back and forwards really fast. How do i fix that?

And another question:

Is it possible for a func_usable to be disabled from using, so that when you press use while targetting it that it doesn't get used, but only when
it gets triggered by another entity?

[Harry Young]

On the camera: All Cameras need the same Targetname and - as described - get cycled in creation-order. To disable flickering you also need to set the wait-value to a redicoulously high number.

On the other issue I am not sure wich of the following you mean. If your Usable dedicated to a visible effect (like alert-lights) set 'team' to '2'. If the usable is dedicated to a system and only meant to be used in specific cases you can either cover it with another caulk-ed usable or give your Usable a targetname2 and have it be targeted by a target_deactivate.

[Martin Thompson]

Thanks for the answers, i already figured it out myself though

I have all cameras now the same targetname, that works.
The wait value is set to a day, so no problem during rp's there . I tried setting it to -1,
but then it flickers after the first time u use it, but now it works.

As for the usable, i covered the entire screen with a func_usable that is used to toggle between views. This way the screen brush usable isn't ever used so the system doesn't bug.

I made a vid of it, it's working pretty sexy now, thanks for you help!

[Harry Young]

Looks very nice ^^