Jump to content

Recommended Posts

Posted (edited)

found some similar topics but no exact advice was given.

Is it possible to move F2 camera a bit backwards ? it feels too close for me.

Which script parameters should be modified to save it 'forever' ?

(default view is on pic#1 and second ya want to save is on pic#2)

Screen_140119_111601.thumb.jpg.7a816dff903d4ce9e866fe0a2eb564c5.jpg

Screen_140119_111608.thumb.jpg.309fe34ef3f5dccf9ef12dd12eb0b169.jpg

Edited by insider
not enough information in the post
  • Like 1
Posted (edited)

Inside "DCS World\Config\View\View.lua" i think, copy this file to "Saved Games\DCS\Config\View\" and edit the file. I can't tell what exactly you have to change so....try & error :blush:

 

Edit: View.lua not Server.lua

Edited by Laro
Posted
Inside "DCS World\Config\View\View.lua" i think, copy this file to "Saved Games\DCS\Config\View\" and edit the file. I can't tell what exactly you have to change so....try & error :blush:

 

Edit: View.lua not Server.lua

 

thx i'll give this a try; there however must be some X/Y/Z camera position coordinates, but don't know which variable !? chase/cockpit/combat is all i've seen...

Posted

You do realize that the F2 view can be zoomed out with the mouse wheel?

ASUS ROG Maximus VIII Hero, i7-6700K, Noctua NH-D14 Cooler, Crucial 32GB DDR4 2133, Samsung 950 Pro NVMe 256GB, Samsung EVO 250GB & 500GB SSD, 2TB Caviar Black, Zotac GTX 1080 AMP! Extreme 8GB, Corsair HX1000i, Phillips BDM4065UC 40" 4k monitor, VX2258 TouchScreen, TIR 5 w/ProClip, TM Warthog, VKB Gladiator Pro, Saitek X56, et. al., MFG Crosswind Pedals #1199, VolairSim Pit, Rift CV1 :thumbup:

Posted

In that case, you might be stuck. That view does not appear to be defined in Vew or Server luas. Chase and Combat views are not F2.

ASUS ROG Maximus VIII Hero, i7-6700K, Noctua NH-D14 Cooler, Crucial 32GB DDR4 2133, Samsung 950 Pro NVMe 256GB, Samsung EVO 250GB & 500GB SSD, 2TB Caviar Black, Zotac GTX 1080 AMP! Extreme 8GB, Corsair HX1000i, Phillips BDM4065UC 40" 4k monitor, VX2258 TouchScreen, TIR 5 w/ProClip, TM Warthog, VKB Gladiator Pro, Saitek X56, et. al., MFG Crosswind Pedals #1199, VolairSim Pit, Rift CV1 :thumbup:

Posted
In that case, you might be stuck. That view does not appear to be defined in Vew or Server luas. Chase and Combat views are not F2.

 

so it must be somewhere i think...

 

 

SnapViews["Su-33"] = {

[1] = {-- player slot 1

[1] = {

viewAngle = 71.824692,--FOV

hAngle = 0.000000,

vAngle = -32.458889,

x_trans = 0.000000,

y_trans = 0.000000,

z_trans = 0.000000,

rollAngle = 0.000000,

},

[2] = {

viewAngle = 38.591434,--FOV

hAngle = 42.504570,

vAngle = -42.790123,

x_trans = 0.000000,

y_trans = 0.000000,

z_trans = 0.000000,

rollAngle = 0.000000,

},

[3] = {

viewAngle = 30.427544,--FOV

hAngle = 0.000000,

vAngle = -41.808968,

x_trans = 0.000000,

y_trans = 0.000000,

z_trans = 0.000000,

rollAngle = 0.000000,

},

[4] = {

viewAngle = 34.392349,--FOV

hAngle = -32.597401,

vAngle = -35.293747,

x_trans = 0.000000,

y_trans = 0.000000,

z_trans = 0.000000,

rollAngle = 0.000000,

},

[5] = {

viewAngle = 87.468338,--FOV

hAngle = 129.012665,

vAngle = 14.547977,

x_trans = 0.000000,

y_trans = 0.000000,

z_trans = 0.000000,

rollAngle = 0.000000,

},

[6] = {

viewAngle = 43.977936,--FOV

hAngle = 0.000000,

vAngle = -4.951577,

x_trans = 0.000000,

y_trans = 0.000000,

z_trans = 0.000000,

rollAngle = 0.000000,

},

[7] = {

viewAngle = 87.468338,--FOV

hAngle = -129.012665,

vAngle = 14.491872,

x_trans = 0.000000,

y_trans = 0.000000,

z_trans = 0.000000,

rollAngle = 0.000000,

},

[8] = {

viewAngle = 87.468338,--FOV

hAngle = 82.862923,

vAngle = -9.500000,

x_trans = 0.000000,

y_trans = 0.000000,

z_trans = 0.000000,

rollAngle = 0.000000,

},

[9] = {

viewAngle = 87.468338,--FOV

hAngle = 0.000000,

vAngle = 38.979362,

x_trans = 0.000000,

y_trans = 0.000000,

z_trans = 0.000000,

rollAngle = 0.000000,

},

[10] = {

viewAngle = 87.468338,--FOV

hAngle = -82.461266,

vAngle = -12.843998,

x_trans = 0.000000,

y_trans = 0.000000,

z_trans = 0.000000,

rollAngle = 0.000000,

},

[11] = {--look at left mirror

viewAngle = 68.786629,--FOV

hAngle = 15.618313,

vAngle = 7.522498,

x_trans = 0.000000,

y_trans = 0.000000,

z_trans = 0.000000,

rollAngle = 0.000000,

},

[12] = {--look at right mirror

viewAngle = 69.165199,--FOV

hAngle = -15.683434,

vAngle = 8.549150,

x_trans = 0.000000,

y_trans = 0.000000,

z_trans = 0.000000,

rollAngle = 0.000000,

},

[13] = {--default view

viewAngle = 87.468338,--FOV

hAngle = 0.000000,

vAngle = -9.500000,

x_trans = 0.000000,

y_trans = -0.115000,

z_trans = 0.000000,

rollAngle = 0.000000,

},

},

}

 

 

 

so what cameras does it define here ?

Posted

Those are in-cockpit snap views. Activated with Numpad0+Numpad[number in bracket].

ASUS ROG Maximus VIII Hero, i7-6700K, Noctua NH-D14 Cooler, Crucial 32GB DDR4 2133, Samsung 950 Pro NVMe 256GB, Samsung EVO 250GB & 500GB SSD, 2TB Caviar Black, Zotac GTX 1080 AMP! Extreme 8GB, Corsair HX1000i, Phillips BDM4065UC 40" 4k monitor, VX2258 TouchScreen, TIR 5 w/ProClip, TM Warthog, VKB Gladiator Pro, Saitek X56, et. al., MFG Crosswind Pedals #1199, VolairSim Pit, Rift CV1 :thumbup:

Posted

cichlidfan

may it then be possible to save F2 camera position after in-game editing ?

can't believe this is not defined by any scripts...

Posted

It's not editable, sorry.

i7 7700K | 32GB RAM | GTX 1080Ti | Rift CV1 | TM Warthog | Win 10

 

"There will always be people with a false sense of entitlement.

You can want it, you can ask for it, but you don't automatically deserve it. "

Posted

I was looking for this too. Couldn't find either.

 

Especially F2 and F6 views suck! Everytime I have to correct the view to see the direction or set the proper zoom... :\

Intel i7-14700@5.6GHz | MSI RTX4080 SuperSuprimX | Corsair V. 64GB@6400MHz. | Samsung 1TB 990 PRO SSD (Win10Homex64)
Samsung G5 32" + Samsung 18" + 2x8"TFT Displays | TM Warthog Stick w/AVA Base | VPC MongoosT-50CM3 Throttle | TM MFD Cougars | Logitech G13, G230, G510, PZ55 & Farming Sim Panel | TIR5 & M.Quest3 VR
>>MY MODS<< | Discord: Devrim#1068

Posted

For F2 you set the zoom once, and as long as you don't change it again it sticks for the rest of the flight.....

i7 7700K | 32GB RAM | GTX 1080Ti | Rift CV1 | TM Warthog | Win 10

 

"There will always be people with a false sense of entitlement.

You can want it, you can ask for it, but you don't automatically deserve it. "

Posted

It would be nice if the Num Enter key centered the external views to default like in the cockpit. From a tracking free camera view I have to change the FOV to see the aircraft, then when I change to F2 view my FOV is all F'ed and I have to adjust the FOV again to fix it. Would be a lot easier to just hit the Enter key to reset it.

Posted

RCtrl+Num Enter resets FOV in all external views.

i7 7700K | 32GB RAM | GTX 1080Ti | Rift CV1 | TM Warthog | Win 10

 

"There will always be people with a false sense of entitlement.

You can want it, you can ask for it, but you don't automatically deserve it. "

Posted
RCtrl+Num Enter resets FOV in all external views.

 

Why are the keys not standardized? There should be one key for resetting FOV in all views. Having two different keys perform the same function in different views is just unnecessary.

  • 4 weeks later...
Posted

This may not be ideal, but you can set a default External FOV in the View.lua. So, you can adjust it to make your view a little further out. On my triple monitor setup I have it set to 145 so I don't always start zoomed way in. Since my screen is so wide, it does not look terrible except for the far edges.

 

-- ExternalViewAngleDefault = 60.0 -- ORIGINAL

ExternalViewAngleDefault = 145.0 -- THIS IS REALLY THE DEFAULT FOV ZOOM TO THE AIRCRAFT.

🍺 Snack Officer  🥨 
Intel I9-10850K (OC @ 5.0ghz) │ 64GB (4x16GB) DDR4 3200 │Gigabyte RTX 4090 Gaming OC 24gb
- ҉ - Blackshark Cockpit Trainer - ҉ -    Thread   | Download

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...