Jump to content

Recommended Posts

Posted

Hey all. So I have set my custom FOV in the F18 by following the instructions on many posts in this forum and YouTube and that is working great. Small problem I have run into now seems new with latest update. I have a slider on my Virpil Throttle set for Zoom View. The slider has a detent at the center position. When I fist start up in the aircraft and set my default FOV by hitting Enter on the numpad everything is good. However, as soon as I use the Zoom View slider to look around cockpit and then return it to center my default FOV is gone and I have to hit Enter again. It doesn't retain that center position on the Zoom according to my default FOV.  You can clearly see the jump as soon as you move the slider.

I've checked the calibration on slider and settings in Virpil software. The detent has a nice deadzone so its not that. No axis to button setting or anything like that. I have no other custom views created. I went ahead and deleted my snapviews.lua and recreated my FOV from scratch to troubleshoot but no difference.

Wish I could do a video but I'm an old fart and don't have those skills.  Anyone have any thoughts?  Thanks and appreciate any help.

 

Posted (edited)

The problem is probably that the slider will be centred at 50%, and your custom FoV does not correspond to that slider position; so as soon as that slider changes its value, the view will snap.

What you could try is not use that custom FoV, and instead set the centre position of the throttle's Z axis to be a value corrresponding to your desired setting; double-click the axis row in the "Axis" view, and then, e.g.,
image.png
to still have the full range of motion, but different scaling on either side of centre. It's a bit annoying since you need to save and "save VPC device" every time to make the change active, but if you keep the software open, then set the slider to a good value in-game, and enter the percentage from the "Axis logical" line, it should work.

Edited by Laurreth
Posted

Thanks @Laurreth

Appreciate the reply.  That's definitely the issue and a reasonable fix but not sure I want to have to make that change every time I change aircraft. I'll have to see how close my FOV is on other planes and if close enough may be able to compromise on a value that works for all.

I did find this in another post but not sure if this can be saved for each aircraft either or becomes a universal setting. And does it create multiplayer problems with passing integrity checks to edit the main views.lua?

On 11/29/2018 at 2:14 PM, Donut said:

Okay everyone...I found the solution!!!

 

Go to DCS World\Mods\aircraft\FA-18C and open the Views.lua file and find the following line near the top...

 

CameraViewAngleLimits = {30.000000,150.000000},

 

 

The default values are 20, 140 which gives a midpoint of 80. I changed it to 30, 150 to give me a midpoint of 90 on my HOTAS zoom axis which now matches by default FOV of 90 that I set.

 

Hope this solution helps!!

 

Posted
4 hours ago, KeyserSoze62 said:

I did find this in another post but not sure if this can be saved for each aircraft either or becomes a universal setting. And does it create multiplayer problems with passing integrity checks to edit the main views.lua?


Editing it on the module’s lua can impact the integrity checks, it is best to copy the server.lua file onto /saved games/dcs/config/view/ and customize it there.

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

  • 4 months later...
Posted

I just purchased the FW190A8 and Spit Mk IX, and am finding that when I spawn, my default spawn zoom position is too narrow.  I edited the SnapViews.lua to make the default zoom 115, which it seems to start at, with the initial fly screen visible.  But when I hit fly, it reverts to about 80.  If I hit the numpad enter key (zoom normal) it goes back to where I want it.  How do I  set it up so the spawn zoom is 115 so I don't have to hit the enter key?

I don't seem to have that problem with my other planes

Talent hits a target no one else can hit, genius hits a target no one else can detect

AMD Ryzen 9 3900x CPU@4.5Ghz, ASUS ROG Crosshair VIII Dark Hero Motherboard, 64GB Corsair Venegence DDR 3200 RAM, MSI Rtx 3060 12GB GPU, MSI Rtx 4060 8GB GPU, 40" and 37" 1920x1080 Samsung Monitor, 40" 1920x1080 Sony Monitor, 1TB Seagate Firecuda M2 PCIe 4 OS SSD, 2TB Western Digital Blue M2 PCIe 3 storage SSD, 8TB Samsung 870QVO storage SSD, Western Digital Blue 1TB storage SATA, 2x Thrustmaster T16000 (LH and RH), Warthog Joy/Throttle/TPRS, 6 x Cougar MFDs (4 with Generic VGA 800x600 displays), Track IR 5 with IR Trackstar V3, Logitech G915 Tactile Keyboard, Logitech G502 Lightspeed Mouse, Logitech G935 Headset, Next Level Racing HF8 Haptic Gaming Pad, Windows 10 Pro 64-bit

Soul: None (sold long ago to the MGOMU, also known as Princess)

Posted
26 minutes ago, Darkdiz said:

I just purchased the FW190A8 and Spit Mk IX, and am finding that when I spawn, my default spawn zoom position is too narrow.  I edited the SnapViews.lua to make the default zoom 115, which it seems to start at, with the initial fly screen visible.  But when I hit fly, it reverts to about 80.  If I hit the numpad enter key (zoom normal) it goes back to where I want it.  How do I  set it up so the spawn zoom is 115 so I don't have to hit the enter key?

I don't seem to have that problem with my other planes


perhaps this post of mine can help you to set the fov correctly:

 

https://forum.dcs.world/topic/291882-patch-notes-discussion-thread-2022/?do=findComment&comment=5081573

 

  • Thanks 1

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted
2 hours ago, Rudel_chw said:


perhaps this post of mine can help you to set the fov correctly:

 

https://forum.dcs.world/topic/291882-patch-notes-discussion-thread-2022/?do=findComment&comment=5081573

 

Hmmm, no luck.  It appears that the server.lua is no longer edited based on the rem statements in it (see below, this is line 16).

16 --this file is no longer should be edited for adding new flyable aircraft , DCS automatically check core database (i.e. where you define your aircraft in aircraft table just define ViewSettings and SnapViews tables)

I looked for a viewsettings.lua (found the snapviews.lua but this doesn't seem to include the default spawn view).

Scratching my head here...

Talent hits a target no one else can hit, genius hits a target no one else can detect

AMD Ryzen 9 3900x CPU@4.5Ghz, ASUS ROG Crosshair VIII Dark Hero Motherboard, 64GB Corsair Venegence DDR 3200 RAM, MSI Rtx 3060 12GB GPU, MSI Rtx 4060 8GB GPU, 40" and 37" 1920x1080 Samsung Monitor, 40" 1920x1080 Sony Monitor, 1TB Seagate Firecuda M2 PCIe 4 OS SSD, 2TB Western Digital Blue M2 PCIe 3 storage SSD, 8TB Samsung 870QVO storage SSD, Western Digital Blue 1TB storage SATA, 2x Thrustmaster T16000 (LH and RH), Warthog Joy/Throttle/TPRS, 6 x Cougar MFDs (4 with Generic VGA 800x600 displays), Track IR 5 with IR Trackstar V3, Logitech G915 Tactile Keyboard, Logitech G502 Lightspeed Mouse, Logitech G935 Headset, Next Level Racing HF8 Haptic Gaming Pad, Windows 10 Pro 64-bit

Soul: None (sold long ago to the MGOMU, also known as Princess)

Posted

Well, not the best option, but I fixed it by deleting the zoom function on the slider axis, and instead put the zoom function as Zoom in/out slow onto another key.

Talent hits a target no one else can hit, genius hits a target no one else can detect

AMD Ryzen 9 3900x CPU@4.5Ghz, ASUS ROG Crosshair VIII Dark Hero Motherboard, 64GB Corsair Venegence DDR 3200 RAM, MSI Rtx 3060 12GB GPU, MSI Rtx 4060 8GB GPU, 40" and 37" 1920x1080 Samsung Monitor, 40" 1920x1080 Sony Monitor, 1TB Seagate Firecuda M2 PCIe 4 OS SSD, 2TB Western Digital Blue M2 PCIe 3 storage SSD, 8TB Samsung 870QVO storage SSD, Western Digital Blue 1TB storage SATA, 2x Thrustmaster T16000 (LH and RH), Warthog Joy/Throttle/TPRS, 6 x Cougar MFDs (4 with Generic VGA 800x600 displays), Track IR 5 with IR Trackstar V3, Logitech G915 Tactile Keyboard, Logitech G502 Lightspeed Mouse, Logitech G935 Headset, Next Level Racing HF8 Haptic Gaming Pad, Windows 10 Pro 64-bit

Soul: None (sold long ago to the MGOMU, also known as Princess)

Posted
On 6/22/2022 at 5:37 AM, KeyserSoze62 said:

Thanks @Laurreth

Appreciate the reply.  That's definitely the issue and a reasonable fix but not sure I want to have to make that change every time I change aircraft. I'll have to see how close my FOV is on other planes and if close enough may be able to compromise on a value that works for all.

I did find this in another post but not sure if this can be saved for each aircraft either or becomes a universal setting. And does it create multiplayer problems with passing integrity checks to edit the main views.lua?

Another possible solution is to setup curve for zoom axis (you have to do it for each aircraft), thus you can have center of physical axis at desired FOV value.

You don't know what you don't know.
Ты не знаешь то, чего не знаешь.

Скрытый текст

Hardware: AMD 5900x, 64Gb RAM@3200MHz, NVidia RTX3070 8Gb, Monitor 3440x1440(21:9), Samsung 980pro 1Tb NVMe SSD, VKB Gunfighter+MCGU, Virpil Throttle CM3, VKB T-Rudder, TrackIR.

 

Posted
On 11/6/2022 at 11:47 PM, Darkdiz said:

Hmmm, no luck.  It appears that the server.lua is no longer edited based on the rem statements in it (see below, this is line 16).

16 --this file is no longer should be edited for adding new flyable aircraft , DCS automatically check core database (i.e. where you define your aircraft in aircraft table just define ViewSettings and SnapViews tables)

 

Server.lua works for me if I place it at /Saved Games/DCS/Config/View ... like this:

 

36IOOxR.jpg

 

My CameraViewAngleLimits are 20 and 210, its Midpoint (Zoom Normal) is (20+210)/2 = 115 degrees.

 

On 11/6/2022 at 11:47 PM, Darkdiz said:

I looked for a viewsettings.lua (found the snapviews.lua but this doesn't seem to include the default spawn view).

 

This is my Snapviews.lua:

 

mGuOyJp.jpg

 

The default view is #13 ... I set FOV to 115.

This is a short video showing how it looks on my DCS:

 

 

 

I placed the view zoom on an axis, and you can see that the maximum zoom is at 210, minimum at 20 and normal is at 115, as expected. 🙂

 

On the video you can't notice, but after seting the zoom axis to mid point, I press Enter ... the view does not change, because the axis mid point and the normal view FOV are the same: 115º

  • Thanks 1

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted

I'll have another look at this, and play around with it, as it seems to be the preferred solution

  • Like 1

Talent hits a target no one else can hit, genius hits a target no one else can detect

AMD Ryzen 9 3900x CPU@4.5Ghz, ASUS ROG Crosshair VIII Dark Hero Motherboard, 64GB Corsair Venegence DDR 3200 RAM, MSI Rtx 3060 12GB GPU, MSI Rtx 4060 8GB GPU, 40" and 37" 1920x1080 Samsung Monitor, 40" 1920x1080 Sony Monitor, 1TB Seagate Firecuda M2 PCIe 4 OS SSD, 2TB Western Digital Blue M2 PCIe 3 storage SSD, 8TB Samsung 870QVO storage SSD, Western Digital Blue 1TB storage SATA, 2x Thrustmaster T16000 (LH and RH), Warthog Joy/Throttle/TPRS, 6 x Cougar MFDs (4 with Generic VGA 800x600 displays), Track IR 5 with IR Trackstar V3, Logitech G915 Tactile Keyboard, Logitech G502 Lightspeed Mouse, Logitech G935 Headset, Next Level Racing HF8 Haptic Gaming Pad, Windows 10 Pro 64-bit

Soul: None (sold long ago to the MGOMU, also known as Princess)

Posted

Sigh, still not working for me, clearly more research to be done.

I changed my Ch13 FOV  on both my Spit MkIX and Anton to 105 (decided that 115 was a little TOO wide), but the view still was far too narrow on spawn (it is somewhere around 60), until I hit NUMPAD Enter, when it then reverted to whatever zoom I put into Ch13.

Even playing around with the server.lua (copied and pasted into my user files folder) didn't seem to work under the cameraviewanglelimits line.

The slider remains unallocated, using a seperate binding for zoom in/out slow until I can sort it out

Talent hits a target no one else can hit, genius hits a target no one else can detect

AMD Ryzen 9 3900x CPU@4.5Ghz, ASUS ROG Crosshair VIII Dark Hero Motherboard, 64GB Corsair Venegence DDR 3200 RAM, MSI Rtx 3060 12GB GPU, MSI Rtx 4060 8GB GPU, 40" and 37" 1920x1080 Samsung Monitor, 40" 1920x1080 Sony Monitor, 1TB Seagate Firecuda M2 PCIe 4 OS SSD, 2TB Western Digital Blue M2 PCIe 3 storage SSD, 8TB Samsung 870QVO storage SSD, Western Digital Blue 1TB storage SATA, 2x Thrustmaster T16000 (LH and RH), Warthog Joy/Throttle/TPRS, 6 x Cougar MFDs (4 with Generic VGA 800x600 displays), Track IR 5 with IR Trackstar V3, Logitech G915 Tactile Keyboard, Logitech G502 Lightspeed Mouse, Logitech G935 Headset, Next Level Racing HF8 Haptic Gaming Pad, Windows 10 Pro 64-bit

Soul: None (sold long ago to the MGOMU, also known as Princess)

Posted
17 minutes ago, Darkdiz said:

Sigh, still not working for me, clearly more research to be done.


Hi,  please attach your server.lua and snapviews.lua to take a look, both from your /saved games/dcs/config/view/ folder … there is no reason this works on my DCS and not on yours

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted

I still have the server.lua (unedited) in my main game folder.

I also found another views.lua file in the mods folder in the main game folder under mods/aircraft, I included the FW190 version as well (there is also a Spitty version). This one may be the issue, as it is very similar to the snapview.lua

SnapViews.lua Views.lua Server.lua

Talent hits a target no one else can hit, genius hits a target no one else can detect

AMD Ryzen 9 3900x CPU@4.5Ghz, ASUS ROG Crosshair VIII Dark Hero Motherboard, 64GB Corsair Venegence DDR 3200 RAM, MSI Rtx 3060 12GB GPU, MSI Rtx 4060 8GB GPU, 40" and 37" 1920x1080 Samsung Monitor, 40" 1920x1080 Sony Monitor, 1TB Seagate Firecuda M2 PCIe 4 OS SSD, 2TB Western Digital Blue M2 PCIe 3 storage SSD, 8TB Samsung 870QVO storage SSD, Western Digital Blue 1TB storage SATA, 2x Thrustmaster T16000 (LH and RH), Warthog Joy/Throttle/TPRS, 6 x Cougar MFDs (4 with Generic VGA 800x600 displays), Track IR 5 with IR Trackstar V3, Logitech G915 Tactile Keyboard, Logitech G502 Lightspeed Mouse, Logitech G935 Headset, Next Level Racing HF8 Haptic Gaming Pad, Windows 10 Pro 64-bit

Soul: None (sold long ago to the MGOMU, also known as Princess)

Posted

Think I got it fixed. Apparently the views.lua in the main game mods/aircraft/aircraft name folder is the answer.

I edited the main game file (not sure if it will pass IC) but also copied it into a newly created folder in my saved games/mods/aircraft/aircraft name folder. Changed line 4 to change 140 to 210.

I disabled the saved games server.lua (renamed it server.old), and it still worked, so I'm not sure this file has an effect.

Obviously a few more tests to be run!

Talent hits a target no one else can hit, genius hits a target no one else can detect

AMD Ryzen 9 3900x CPU@4.5Ghz, ASUS ROG Crosshair VIII Dark Hero Motherboard, 64GB Corsair Venegence DDR 3200 RAM, MSI Rtx 3060 12GB GPU, MSI Rtx 4060 8GB GPU, 40" and 37" 1920x1080 Samsung Monitor, 40" 1920x1080 Sony Monitor, 1TB Seagate Firecuda M2 PCIe 4 OS SSD, 2TB Western Digital Blue M2 PCIe 3 storage SSD, 8TB Samsung 870QVO storage SSD, Western Digital Blue 1TB storage SATA, 2x Thrustmaster T16000 (LH and RH), Warthog Joy/Throttle/TPRS, 6 x Cougar MFDs (4 with Generic VGA 800x600 displays), Track IR 5 with IR Trackstar V3, Logitech G915 Tactile Keyboard, Logitech G502 Lightspeed Mouse, Logitech G935 Headset, Next Level Racing HF8 Haptic Gaming Pad, Windows 10 Pro 64-bit

Soul: None (sold long ago to the MGOMU, also known as Princess)

Posted
13 hours ago, Darkdiz said:

I still have the server.lua (unedited) in my main game folder.

 

Hi. That's not the proper way to customize your view settings ... the following are instructions given by ED's team member on this Forum, that I saved on my notes file:

"1. Views. 

We create the Saved Games \ DCS \ Config \ View \ directory and put three files in it (you can copy them from the installed simulator):

View.lua
Server.lua
SnapViews.lua

Files are edited to taste, the values of variables and constants are used instead of native".
 

The above means that you DO NOT edit the view luas on the DCS program folder, instead copy them to the path shown at /Saved Games/ and edit them there.

 

13 hours ago, Darkdiz said:

I also found another views.lua file in the mods folder in the main game folder under mods/aircraft, I included the FW190 version as well (there is also a Spitty version). This one may be the issue, as it is very similar to the snapview.lua

 

The views.lua file included with each aircraft Module is like a template, do not modify it, instead copy its "View Settings" content onto your Server.lua located at /Saved Games/ (unless it is already there), you will need to manually add the aircraft identification, like this:

ViewSettings["FW-190A8"] = {

instead of

ViewSettings = {

 

The Snapviews.lua enties are automatically created when you save any snapview when you are seated on the aircraft, uou just modify them afterwards, using a text editor.

 

  • Thanks 1

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted

OK, thanks. I'll copy the above into my notes binder, and re-edit

Talent hits a target no one else can hit, genius hits a target no one else can detect

AMD Ryzen 9 3900x CPU@4.5Ghz, ASUS ROG Crosshair VIII Dark Hero Motherboard, 64GB Corsair Venegence DDR 3200 RAM, MSI Rtx 3060 12GB GPU, MSI Rtx 4060 8GB GPU, 40" and 37" 1920x1080 Samsung Monitor, 40" 1920x1080 Sony Monitor, 1TB Seagate Firecuda M2 PCIe 4 OS SSD, 2TB Western Digital Blue M2 PCIe 3 storage SSD, 8TB Samsung 870QVO storage SSD, Western Digital Blue 1TB storage SATA, 2x Thrustmaster T16000 (LH and RH), Warthog Joy/Throttle/TPRS, 6 x Cougar MFDs (4 with Generic VGA 800x600 displays), Track IR 5 with IR Trackstar V3, Logitech G915 Tactile Keyboard, Logitech G502 Lightspeed Mouse, Logitech G935 Headset, Next Level Racing HF8 Haptic Gaming Pad, Windows 10 Pro 64-bit

Soul: None (sold long ago to the MGOMU, also known as Princess)

Posted

Seems to work, thanks @Rudel_chwfor the help!

Funny how the lua worked fine once I got the syntax sorted out (had the FW correct, but forgot to put the Spit name in between "", one worked, one didn't. Go figure!)

Still have to fine-tune initial head position, I feel I'm a tad too far back, but that is for another day!

Talent hits a target no one else can hit, genius hits a target no one else can detect

AMD Ryzen 9 3900x CPU@4.5Ghz, ASUS ROG Crosshair VIII Dark Hero Motherboard, 64GB Corsair Venegence DDR 3200 RAM, MSI Rtx 3060 12GB GPU, MSI Rtx 4060 8GB GPU, 40" and 37" 1920x1080 Samsung Monitor, 40" 1920x1080 Sony Monitor, 1TB Seagate Firecuda M2 PCIe 4 OS SSD, 2TB Western Digital Blue M2 PCIe 3 storage SSD, 8TB Samsung 870QVO storage SSD, Western Digital Blue 1TB storage SATA, 2x Thrustmaster T16000 (LH and RH), Warthog Joy/Throttle/TPRS, 6 x Cougar MFDs (4 with Generic VGA 800x600 displays), Track IR 5 with IR Trackstar V3, Logitech G915 Tactile Keyboard, Logitech G502 Lightspeed Mouse, Logitech G935 Headset, Next Level Racing HF8 Haptic Gaming Pad, Windows 10 Pro 64-bit

Soul: None (sold long ago to the MGOMU, also known as Princess)

  • Recently Browsing   0 members

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