Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BEAM Not apearring #126

Open
ghost opened this issue Jan 14, 2024 · 12 comments
Open

BEAM Not apearring #126

ghost opened this issue Jan 14, 2024 · 12 comments

Comments

@ghost
Copy link

ghost commented Jan 14, 2024

Hello. The issue I have is that I can play the game, but the Beam that comes out from the portal gun does not appear, I checked the setting and the aim assist is on 2 so it should appear.
I noticed that in the VR game's top left corner, I can see a normal crosshair and when the portal gun is aiming at the center top half of the screen, the classic crosshair from the no VR version of the game appears.

I am playing on an Oculus Quest 2 in 72hz and 4128x2096

@FreaKzero
Copy link

FreaKzero commented Jan 14, 2024

Have the same Problem:

Versions:
I tried 1.5.0 and 0.2.0 preview.1 version - playing the vanilla version of Portal 2

Hardware:
PICO 4 (Wired via Streaming Assistant) / RTX 3070

Startup Method:
Tried directly via Windows Shortcut - as also directly via SteamVR Interface (yep - used the Startupparameters on both)

also tried to reset my cvars with

sv_cheats 1
reset_gameconvars

AimMode in the VR configfile is set to 2
When im looking directly up to the ceiling (and only then) - the "original crosshair" appears (blue/yellow one) - but no lasers
with crosshair 0 - also the original crosshair disappears

@ghost
Copy link
Author

ghost commented Jan 14, 2024

WOW! is the same over here, no matter which version I try the same problem occurs

@xenon2
Copy link

xenon2 commented Jan 15, 2024

Same.

Reverb G2 / 3080 TI

Funny thing is, it worked like 2 weeks ago, maybe some update on assets.

@FreaKzero
Copy link

FreaKzero commented Jan 15, 2024

Same.

Reverb G2 / 3080 TI

Funny thing is, it worked like 2 weeks ago, maybe some update on assets.

I just installed Portal 2 "fresh" 2 days ago (after i played it last in about 2012) and installed the mod also that day.
Just found out about that Beams in YouTube videos which were recorded longer time ago. (and thought that aiming is very hard)
So your assumption what the assets belong - seems to make sense.

Do you guys also have the "original Crosshair" when you directy look up to the ceiling ?

@FUNtasticOne
Copy link

FUNtasticOne commented Jan 16, 2024

I am experiencing the same problem on two different PCs. I have already played the Portal 2 VR mod on both PCs without any problems, but when I tested it again yesterday, I have the problem that the crosshair is missing, but it can be seen normally in the top left corner.
If you look at the image on the monitor while playing and after loading a level, you have a second area in the top left of the displayed image section, in which the same image is displayed again, a picture within a picture, so to speak. If you look at it, you'll understand what I mean. It seems that the second, smaller image area coincides with the area in the headset in which the crosshairs are displayed correctly.

What I have already tried:
Set a higher resolution in the start parameters for Portal 2.
Changed the resolution of my monitor and set the scaling options to 100%.
Reinstalling Portal 2 and the VR Mod.
A few days ago there seems to have been an update of Portal 2 in Steam. I rolled back Portal 2 to the previous version via beta options.

None of this has solved the problem.

The problem occurs with both the Quest 3 and the Pico 4. One PC with RTX 3090, the other with RTX 4070, each with the latest driver version.

I wanted to play a bit of Portal 2 with a friend using both PCs and the two headsets. I'm a bit glad that I'm not the only one with this problem, and I would be very happy if there is a solution.

@FreaKzero
Copy link

For what i saw - on the 5th of January, Portal 2 got an Update with following entries:

  • Fixed several remote code execution and crash exploits against co-op partners. All reported via HackerOne.
  • Fixed a regression in targeting some entities with the ping tool.

@FUNtasticOne
Copy link

For what i saw - on the 5th of January, Portal 2 got an Update...

Yes, it will most likely have something to do with that. What surprises me is that I selected the previous stable release in the beta version settings in Steam for Portal 2. As a result, the update from January was uninstalled, I had a game version from 2021 installed, apparently the version from before the last update.
I then copied the files for the VR mod again.
Unfortunately, this did not solve the problem. Presumably the only hope is that someone will have a look into it for troubleshooting.

@Kailatte
Copy link

I also have the problem that the Beam does not appear. Unfortunately, the game is not playable this way. Do you think there is a chance that this error will be fixed? At the moment it looks like the project is dead, which would be a shame.

@skylon07
Copy link

I'm having the same exact issue, and also the blue/orange portal "glowing" effects (and the electric grabbing effects) seem to be incorrectly translated away from the portal gun (the rotation seems to match though).

One workaround for the aiming: I found that you can use the top black prong as a pretty good aiming sight if you hold the portal gun straight out in front of you (either gangster-style or oriented upright). I found myself only needing to do this for far-away shots, but it's been somewhat consistent for me so far, and much better than a spam-shoot-make-a-small-adjustment-and-shoot-again-twenty-times strategy.

@Sniper257
Copy link

Fix for this is the same as the fix for #125 (comment), roll back to build 11097438 and the beam and level progression is working again.

@BrokenMemory731
Copy link

BrokenMemory731 commented Jul 14, 2024

@Sniper257 What is the manifest id for that version? (or the date). And what VR mod version should I put in it?

@CrazyKitty1226
Copy link

Fix for this is the same as the fix for #125 (comment), roll back to build 11097438 and the beam and level progression is working again.

doesnt do anything for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants