RA2 V1.4 DSL V2.2: Drunk Camera Man

[ShayminSky]

NOTE, I use bold text to highlight my key problems. (though It would still be great if you read the whole thing)

A few months back I switched to windows 10 and have now reinstalled RA2 (with the DSL mod V2.2). To my surprise I can’t lock the camera behind my bot for the life of me. I “dealt” with the camera problems as best as I could for about a week and a half. However, with the creation Velocipede (stabby bot) I can’t take it anymore. I really could use and appreciate some help! But first, to save time I’m going to list what I've already tried…

1. Tried without DSL mod
2. Ran as administrator
3. Used Windows XP service pack 3
4. Set Resolution to 1024x768
5. Set Resolution to 640x480
6. Set Resolution to 1280x1024
7. Manually set resolution to 1440x900 (My monitors native resolution) via the "ra2.cfg" with notepad ++
8. Removed and redownloaded RA2 4 times
9. Downloaded “DSL2.2complete”
10. Installed “RA2_Patch_V13”
11. Changed the camera from orbit to static to watch
12. Set priority to high in task manager
13. Pressed F1, F2 (obviously) F3, F4, F5, F6, F7, F8, F9, F10, F11... AAAND F12 (We'll get back to this one later...)
 
None of these have worked or helped in the slightest, Though I do have some notes I’d like to add too possibly clear any confusion.

1. I have two monitors
2. It’s file location is on my desktop not Programs Files
3. Non CD/.EXE Installation 
4. All resolutions have been tried in x16 and x32 resolutions, AKA fullscreen
5. Though this is on windows 10, My windows 8.1 machine has the same problem

Lastly, a weird but VERY important note that could potentially fix this problem, When I press F12 the camera locks precisely how I want it. However, F12 turns on a grid mode that not only lags the game, but is visually unappealing to the eyes and has a chance (In my experience) to crash the game. My solution would be to change grid modes key binding from F12 to a different key (Though it would be really nice to just fix it outright). Hopefully I posted in the right place (this is my first time on this forum). Thanks for the help!

Computer Specs:
GPU: GTX 780 Ti (SuperClocked)
CPU: Intel Core i7 Extreme Edition i7-5960X
RAM: 4x4GB, 3200MHZ
PSU: 2500W
HD: SSD hybrid 300GB
OS: x64 Windows 10

[09090901]

welcome to GTM

In regards to the camera not following your robot, the general consensus for this issue seems to be that your PC is too powerful. Nobody knows why this is, but Ra2 is old and is a weird game like that.  I also have the same issue on windows 7, so it more than likely has something to do with the hardware. Unfortunately I don't think that there is a solution to this, so your only option would be to use the other camera angles.

F12 just shows the collision mesh of components and the arena

[Badger]

Note that a lot of custom arenas don't have any good camera angles, so your best bet is downloading the action camera and use that (by pressing F3 and F4 at the same time)

[ShayminSky]

welcome to GTM

In regards to the camera not following your robot, the general consensus for this issue seems to be that your PC is too powerful. Nobody knows why this is, but Ra2 is old and is a weird game like that.  I also have the same issue on windows 7, so it more than likely has something to do with the hardware. Unfortunately I don't think that there is a solution to this, so your only option would be to use the other camera angles.

F12 just shows the collision mesh of components and the arena

Is there anyway to change F12 from collision mesh? Because like I said "When I press F12 the camera locks precisely how I want it."

[Reier]

It only locks the camera because it lags your game because it shows the collision mesh which takes more processing power

[ShayminSky]

You'd think that, However when I'm in the robot workshops testing area and I turn it on, the game does not lag in the slightest, nor does it show the grid. Another HUGE thing to note that I found out is when I set the priority to high in the task manager, It no longer lags when I activate grid mode, In fact I'm going to record a video to help solve the problem!

[Badger]

That's not the issue shaymin.

The follow (F2) camera breaks if your game runs too fast. Showing collision meshes (F12) makes your game slow down, allowing the F2 cam to work again. The best solution in this situation is to use the action cam.

[ShayminSky]

Another thing I'd also like to add given the benefit of the doubt, let's say it is because my PC is too powerful, In my experience it has to due with frame rates, My game in a fight (we'll say against grognak the vengeful, In the default combat arena) When I don't have grid mode active I get about 1100-1500 FPS, When grid mode is active I get about 50-80 FPS, That's when it locks the camera, So in essence you are right, However can you lock the frame rate some how? I will go to just about any extent to play this game. Another thing to note, This game work just fine with the same hardware when I was forced to use a 32 bit version of windows 7. 

[Badger]

Another thing I'd also like to add given the benefit of the doubt, let's say it is because my PC is too powerful, In my experience it has to due with frame rates, My game in a fight (we'll say against grognak the vengeful, In the default combat arena) When I don't have grid mode active I get about 1100-1500 FPS, When grid mode is active I get about 50-80 FPS, That's when it locks the camera, So in essence you are right, However can you lock the frame rate some how? I will go to just about any extent to play this game. Another thing to note, This game work just fine with the same hardware when I was forced to use a 32 bit version of windows 7.

Yes, the power of your machine is directly linked to framerate. I'm not sure if framerate-limiting software will help but its worth a go

[ShayminSky]

Eureka! (Not the Vacuum) When I record with fraps, It drops the FPS down to 300 (despite being set to 30FPS) The camera man is still a little tipsy but is bearable, Only this is, I can't be recording the game 24/7, Though yes I'm going to try a FPS lock program!