spectator_activate_with_resolution 640 360 -p -640 -360 in autoexec doesn't move screen#885
When run from the command line, it works fine. From autoexec, it doesn’t. Suggested by the developer that it might not be passing the variables.
Setting a wait command doesn’t help.
Executing it as the last instruction in autoexec, and placing a wait 1 before it makes it work for me
I don’t know what to tell you. It isn’t working for me even with the wait command. I couldn’t attach the gif file here, so I emailed it to you.
This will be fixed in the next patch. However, a better solution for what you’re doing is to activate it as a screen on your second monitor (either using +spectator_screen or with the -d flag on spectator_activate_with_resolution). You can then bring your OBS windows (and whatever other stream monitoring windows you have) forward; clicking in the main game window does not force the other screen to come forward. Set your OBS to game or window capture this other screen and you have full-resolution spectator restricted view.
If I set it to game, it will likely pick up the actual game window and not the spectator window. If I set it to window, then when I bring the other items forward, it will show them.
Just tested it and yup. This doesn’t work. Also, there is a small space with icons on it that I need to access that the secondary unity window covers up (and there is no way to minimize said window I think).
This is with using +spectator_screen. I didn’t try it with the -d, but I figure the same results will happen.
For the game capture, note that the card in the hand can be seen. It’s not set to spectator.
Game capture, capture specfic window, on the unity secondary display, will show only the game. Can’t do anything about showing desktop icons though.
That command doesn’t exist.
Ok.. For the last time…
Please go from left to right here..
- Note that this is the break between monitor 1 and 2.
- Note that the card on the spectator view should be hidden (This is using +spectator_screen)
- Note that the window doesn’t reflect what is being shown on the background screen.
- Note that it’s using the unity secondary display.
Now, as I have said, there’s an issue. Personally, I would love to just have a second program that all it did was read the main program and display the camera or be spectator or not like the picture in picture. Like a tool that Iian described on his stream.
I’m done trying to test out how to get a full screen experience with OBS. The way I set it up works, though it’s not the best. Well, it will work when it is fixed in the next update.
Sorry, but I’m spending way to much time testing this stuff without being paid for it. :)
mis-remembered: spectator_restrict_view
you would find this yourself if you used the help command. you can narrow down the list of returned help functions by using “help spectator_” at which point it will show a list of commands that start with “spectator_”
Not getting paid either. I was asking to see if the suggestion worked - clearly it didn’t. Good to know. No need to be condescending about it.
Sorry.. I am fustrated at this as I went in 3-4 times into a machine remotely, set it all up and get the pictures, then close it down. It’s a long process. Having someone come in and say, “Try this” and gives the wrong info is fustrating when they are a mod.
This should be an easy thing to test. Run OBS and try things out until it works because there seems to be an issue that Iian isn’t understanding.
I have posted picture proof of the issue and his suggestion just flat out doesn’t work. That’s fine, but if the developer reconizes it as a bug, a moderator shouldn’t try to short circuit the conversation being had about what is and isn’t working.
I realize you aren’t getting paid either. Telling me I could’ve found this out myself isn’t helpful either because I trusted you to understand enough to get involved in this conversation.
You agreed to do this work for your status. I have no status and didn’t agree to beta test this product like this. I told Iian the issue. He said he would fix it and here is a solution that should work. I showed him it didn’t and that was the end of it.
Can we just end this and I’ll wait for the fix and just deal with the other issues in some way? Thanks.
Did selecting the spectator window specifically in game capture as Iain recommend work?
Oh.. I forgot to answer this for you..
… … thanks
The original issue has been fixed as per my earlier comment, everything I’ve posted since has been me trying to help you with OBS. This isn’t a TTS issue, this is a you-configuring-OBS issue. TTS shows the spectator view in your other monitor, and allows any other window you want to be visible above it, while you play in the primary monitor. The setting screwing you up is likely the one I’ve highlighted. If you can’t get it to work in there, then you can try Window Capture using the “Windows Graphics Capture” method. If you still can’t get it to work with that then please go to an OBS forum and ask for assistance, or report a bug in OBS.
This issue is closed.