STAR WARS™: Rogue Squadron 3D

STAR WARS™: Rogue Squadron 3D

Camera zooming out super far
Right, like the title says. The camera is zooming out super, super far away for me on the first level to the point where the game is unplayable because the camera isn't following the x-wing. Does anyone know how to fix this?


PROBLEM SOLVED BY SWITCHING CAMERA ANGLES AROUND
最后由 [] ¬ []1 TEFLON DON 永遠のトランプ 编辑于; 2016 年 4 月 1 日 下午 1:55
< >
正在显示第 16 - 22 条,共 22 条留言
TheShasta1 2016 年 4 月 11 日 下午 3:45 
Thanks Jacko, and to Proofreadhale for the fix!
TurboGarbage 2016 年 4 月 15 日 下午 9:45 
Yeah, wish there was a proper fix for this, even setting camera angle with the F# keys seems to occasionally begin zooming out after accelerating.
superchen37 2018 年 6 月 5 日 下午 8:08 
So I think this might help people who are still experiencing this issue.

Before I begin to discuss how the issue affects the ships, I'll describe the three main camera angles:
1) F3 - Default View upon spawning
2) F8 - Cockpit View
3) F1 - Alternate View: The camera either zooms in on the ship from the back OR flattens the view of your ship.

Of all the vehicles in the game, we can split them into different classes relating to the camera angles and their reaction to the glitch.

Class 1: No fix needed. You are free to use the thrust button regardless of cutscene/death using the default camera angle.
1) Naboo Starfighter
2) TIE Interceptor

Class 2: You need to hit F1 upon spawning (or F8), but the zoom glitch fixes after one cutscene/death. You are then free to use the default camera angle from that point forward until the end of the level.
1) A-Wing
2) Y-Wing*

Class 3: You will have to alternate between the F1 and F3 camera angles after every cutscene/death.
1) X-Wing
2) V-Wing
3) Millennium Falcon

Class 4: No fix available, and the F1 camera angle also suffers from the glitch, requiring you to stay in Cockpit View (F8).
1) Speeder

I placed an asterisk on the Y-Wing because I have found that it has sometimes exhibited Class 3 behavior. I'm still trying to determine definitively which class it truly belongs to.

The T-16 Skyhopper, only available in the Beggar's Canyon bonus level, is either Class 2 or 3. For every death, however, you spawn at the beginning of the level to start the race over, meaning you effectively have to fly with the more intrusive F1 angle every time you play it.

For ships in Classes 2 and 3, what is meant by cutscene does not include the opening cutscene just before you spawn into the level. Additionally, after every cutscene/death, the camera angle will remain to whichever one you set it to, meaning you will have to switch (unless you are using a Class 2 ship, meaning you only need to switch once for the entire duration of the level). Sometimes, if you switched angles prior to a cutscene, the glitch will occur after you resume control and you will have to wait until another cutscene/death for the issue to resolve.

Another thread on this topic noted of playing the game in windowed mode using another program which bypasses the issue entirely, but the frame rate goes down depending on the size of the window.

I know this is quite a long post, but I just wanted to detail some ways to get around this annoying glitch and I hope it helps.
最后由 superchen37 编辑于; 2018 年 6 月 6 日 下午 4:37
delta 2018 年 6 月 10 日 上午 1:12 
I don't think I ever had any camera issues with the speeder...or if I did then I just switched over to the alternate view (which is what I do for all the other ships) and that fixes it.
superchen37 2018 年 12 月 8 日 下午 7:19 
引用自 delta
I don't think I ever had any camera issues with the speeder...or if I did then I just switched over to the alternate view (which is what I do for all the other ships) and that fixes it.

So I just did some actual proper testing on the Speeder and it turns out that it's in Class 3 (alternate camera angles between deaths/cutscenes), meaning Class 4 does not actually exist. Thanks for making your observation, because otherwise I never would have realized it.
finalhope227 2019 年 6 月 12 日 上午 9:19 
SOLUTION:
You can use RivaTuner Statistics Server to lock framerate to 60 fps.

You don't even need Afterburner, just be sure to set a framerate limit at 60 and check the "Shown own statistics" in RivaTuner.

This fixed the F1 view mode for me! :)
Gamephreak5 2019 年 6 月 21 日 下午 12:56 
引用自 finalhope227
SOLUTION:
You can use RivaTuner Statistics Server to lock framerate to 60 fps.

You don't even need Afterburner, just be sure to set a framerate limit at 60 and check the "Shown own statistics" in RivaTuner.

This fixed the F1 view mode for me! :)
I tried this solution and it did nothing for me. Still had the camera glitch. Does it have to be on Vector 2D, Vector 3D, or Raster 3D?
< >
正在显示第 16 - 22 条,共 22 条留言
每页显示数: 1530 50