Camera position problem when in multiplayer.

[Ryan Legend]

Hello,

 

Maybe a few monts ago, I don't know exactly, I started to have problems with the position of the camera in the cockpit. This problem only occurs in multiplayer. When I spawn, the position of the camera is slightly lower then when normal. So, when I press Lctrl + Spacebar, to "unlock" the gun trigger, the camera should automaticly position itself infront of the gun sight. however, in my case it places itself infront of that brown sphere like thing, directly below the gunsight.

 

Also, pressing 0+3 on the numpad doesn't point the camera to the switches on the rightside panel. Same goes for every other number combination, like 0+1, leftside panel. The camera does not respond to these keycommands.

 

I've been trying to overcome the problem by manualy placeing the camera infront of the gun sight and the switches by deactivating the mouse click cockpit and moving the camera to it's correct and normal position. But it is still very frustrating.

 

Thanks in advance,

Ryan.

[zaelu]

What plane exactly?

 

You have 2 files in /DCS World/Config/View/

 

Server.lua and Snapviewsdefault.lua

 

The first controls the angles, cokpits position, 6DoF limits the second controls the default view and other 12 snapview positions (like in FSX where you have different views snapped on some of the instruments)

 

These 2 files are duplicated in case of modding or user defined snapviews in:

 

C:\Users\YOUR WINDOWS USER NAME\Saved Games\DCS\Config\View\

 

Actually the snapviewsdefault.lua is renamed snapviews.lua as is now a user set values file and not the default, although it can be completely identical file with the one mentioned above.

 

Also

 

Each new module after Flaming Cliffs 3 has a file usually named "views.lua" (in Mig21 case is 03_views.lua, don't ask why :) ) that contains same values in almost same syntax as Server.lua and Snapviews.lua but put together in one single file that controls only that module.

 

those views.lua files are usually found in:

 

\DCS World\Mods\aircraft\Plane Name\ (for Mig21 is \DCS World\Mods\aircraft\MIG-21BIS\Entry\ )

 

or... in some cases

 

\DCS World\CoreMods\aircraft\Plane Name\

 

 

So what can you do?

 

Simplest way is to delete those files or put them away from their original folders then do a DCS World repair (make sure you disabled mods before if you have and especially note if you have mods that affect those files as restoring them might make your problem reappear).

 

Then, DCS World will re-download your files with default values.

 

Also. I hope you still reading :), some servers have enforced values for those settings and if by multiplayer you mean one single server it might be the case of a wrong settings enforced by that only server admin.

Edited August 2, 2015 by zaelu

[Ryan Legend]

Zaelu,

 

Thank you very much for your reply.

 

As for the aircraft type, I meant the MiG - 15Bis. (Next time I'll post something, I will make sure that I named the aircraft type that I'm talking about :) )

The problem only occurs in multiplayer and the only server I used with the MiG15 is the KOREAN WAR server. Maybe you're right and the problem is caused by the enforced server values.

 

I will try the MiG on another server today and see if that helps. If it helps and the problem is indeed caused by the KOREAN WAR server, should I contact the server hoster/owner?

 

Thanks again for your time and help.

[Ryan Legend]

I just went on the aerobatics server, hopped in the mig15 and everything worked splended. So, I guess it is a server related issue. to bad though, I really like the KOREAN WAR server.

 

zaelu and blooze, thank you for your help.

I have the answer that I was looking for :) .

 

Ryan.