One of the levels I'm currently working on for the portal stories mod (LP_WIP_2) involves a button which opens a door quite far away. To make it more obvious what that button did I installed a world portal there, with some panels opening in front of it.

However, I wanted to make it more clear, by parenting a func_camera to a func_tracktrain so people can see where that door opens. HOWEVER. When I do that the camera is pretty bad, it has a really really bad resolution, you can only make out a few pixels and it actually makes it a lot worse. So I wondered: are there any other ideas how to do this more smoothly? Now you might think something like ?! it's working fine for me? Yes, it might be, but I THINK that the screen should be a bit big, so my screen was 192x128 px (eat that nasty old cellphone!!!) to make the tv_screen texture fit it

I could also just remove the panels, and use a trigger_look to enable/disable the worldportals. There is however a small possibility that you can actually see the worldportal close with optimal portal placement and it'll be extremely hard to fix that.

What do you think?

Thanks for any help!
~Lp

~Lp

spongylover123 wrote:
How about a func_monitor

OH BRILLIANT! I COULD HAVE NEVER THOUGHT THAT MYSELF!
-Sarcasm self test completed.

Edit:
(Maybe actually READ the title and the contents of the first post? That usually gives you an indication of the issue, so "Gow about a func_monitor?" is a stupid reaction, since I was talking about the resolution of the func_monitor. func_monitor can't be the solution of the problem I have with the func_monitor.)

conclusion: Please read a bit more careful before making this kind of posts. Agree, my wording in the fist message is a bit of a mess. but still...

lpfreaky90 wrote:
Subject: func_monitor resolution
spongylover123 wrote:

How about a func_monitor

OH BRILLIANT! I COULD HAVE NEVER THOUGHT THAT MYSELF!
-Sarcasm self test completed.

Edit:
(Maybe actually READ the title and the contents of the first post? That usually gives you an indication of the issue, so "Gow about a func_monitor?" is a stupid reaction, since I was talking about the resolution of the func_monitor. func_monitor can't be the solution of the problem I have with the func_monitor.)

conclusion: Please read a bit more careful before making this kind of posts. Agree, my wording in the fist message is a bit of a mess. but still...

I wasn't specific enough, I meant to use multiple func_monitors.
64 x 64 is the size of the texture, so just use 9 point cameras 64 units apart and 9 64 x 64 func monitors pointing to each camera.
Unless you're talking about making the resolution better on one focused area, then try to edit a vmt and make a bigger vtf.

spongylover123 wrote:
I wasn't specific enough, I meant to use multiple func_monitors.
64 x 64 is the size of the texture, so just use 9 point cameras 64 units apart and 9 64 x 64 func monitors pointing to each camera.
Unless you're talking about making the resolution better on one focused area, then try to edit a vmt and make a bigger vtf.

Your first idea won't work since the source engine is limited to just one point_camera active at the same moment.

The second thing is that the vmt points to $basetexture = _rt_camera (something like that, don't know the thing for sure). To be able to use a texture as a func_monitor its $basetexture has to be that _rt_camera file. PROBLEM: that vmf isn't in portal 2. And the resolution will never be better than 256x256... So that func_monitor thing just ain't gonna help me. A func_worldportal will though

~Lp

Skotty wrote:
Not if you make just "a part" of the monitor texture on a monitor. Like making a brush, fitting the monitor surface to it and clipping it in 4 single parts.

Won't I still lose my resolution?
~Lp