Zoom out 2D view?
-
I’ve edited my 3D view FOV to 110 degrees since I am now using a triple-screen setup… and I’ve also edited my display resolution so that the 3D world screen stretches across 3 monitors. However, going to the 2D cockpit view, I am too close to the HUD. Is there any way to zoom out the 2D cockpit view? Thanks!
-
I’ve edited my 3D view FOV to 110 degrees since I am now using a triple-screen setup… and I’ve also edited my display resolution so that the 3D world screen stretches across 3 monitors. However, going to the 2D cockpit view, I am too close to the HUD. Is there any way to zoom out the 2D cockpit view? Thanks!
why use 2d?
If u have trackir use Yassy profile which makes head centering more accurate and u are ok.
-
I use 2D as a combined “pause TrackIR and zoom in” function… for when I need to concentrate dropping bombs or some such wherein the increased SA of TIR isn’t really needed.
-
The FOV in 2D (which are actually 3D pre-defined snapviews) is currently not changeable from within the sim itself. But all views are defined within the “3dckpit.dat” files for each aircraft, so you could manually edit the files to change the FOV.
Open one of the 3dckpit.dat files in <bms>\Data\Art\ckptart* and scroll down until you find lines that begin with “guidedview”, e.g. like this"
guidedview 0 0.000000 0.000000 0.000000 -0.000000 1.791412 0.000002 59.999996 0 23 9000 29 18000 1 27000 26 ‘HUD - up once’
The part which I marked in red (always the 8th entry after ‘guidedview’) is the FOV for that view, 60 in this case (don’t mind the rounding error). Enter you new value here as you like and check it out. Of course, you would need to do and test it for each view, which will be quite time-consuming, because once you adjusted the FOV, you usually find that it would be good to change the actual viewpoint as well…
There is a quicker method of finding the correct guidedview entry for your specific needs. Simply use the 3D pit in the sim, adjust the FOV and look in the direction that you like to have as a 2D/guidedview, and then open a chat line (Shift+T by default) and type -without quotes - “.gvd” which is short for “.guidedviewdump”. Now, when you leave BMS and navigate to the <bms>\User\Logs directory, you will find a file named “GuidedView.txt” there, which will include the correct ‘guidedview’ line for the position where you made the .gvd dump in the 3D pit. There are some placeholders in that line, simply use the original values from the line that you like to replace in the 3dckpit.dat file to fill the placeholders.
It sounds more complicated than it actually is, just check it out.</bms></bms>
-
Thank you for that Dunc. PC is out of commission for a few days as I await a replacement part, but I will try it out.
-
The FOV in 2D (which are actually 3D pre-defined snapviews) is currently not changeable from within the sim itself. But all views are defined within the “3dckpit.dat” files for each aircraft, so you could manually edit the files to change the FOV.
Open one of the 3dckpit.dat files in <bms>\Data\Art\ckptart* and scroll down until you find lines that begin with “guidedview”, e.g. like this"
guidedview 0 0.000000 0.000000 0.000000 -0.000000 1.791412 0.000002 59.999996 0 23 9000 29 18000 1 27000 26 ‘HUD - up once’
The part which I marked in red (always the 8th entry after ‘guidedview’) is the FOV for that view, 60 in this case (don’t mind the rounding error). Enter you new value here as you like and check it out. Of course, you would need to do and test it for each view, which will be quite time-consuming, because once you adjusted the FOV, you usually find that it would be good to change the actual viewpoint as well…
There is a quicker method of finding the correct guidedview entry for your specific needs. Simply use the 3D pit in the sim, adjust the FOV and look in the direction that you like to have as a 2D/guidedview, and then open a chat line (Shift+T by default) and type -without quotes - “.gvd” which is short for “.guidedviewdump”. Now, when you leave BMS and navigate to the <bms>\User\Logs directory, you will find a file named “GuidedView.txt” there, which will include the correct ‘guidedview’ line for the position where you made the .gvd dump in the 3D pit. There are some placeholders in that line, simply use the original values from the line that you like to replace in the 3dckpit.dat file to fill the placeholders.
It sounds more complicated than it actually is, just check it out.</bms></bms>
short for “.guidedviewdump”. Now, when you leave BMS and navigate to the <bms>\User\Logs directory, you will find a file named “GuidedView.txt” there, which will include the correct ‘guidedview’ line for the position where you made the .gvd dump in the 3D pit. There are some placeholders in that line, simply use the original values from the line that you like to replace in the 3dckpit.dat file to fill the placeholders. It sounds more complicated than it actually is, just check it out.
I have a request. Can you send me a file where you write in your post, to a private email? As I downloaded BMS, after installing it was not such a file in my given location. Probably because I do not work in panning view using the numeric keypad</bms>
-
External view with the keyboard works normally, the mouse wheel zoom is ok.
-
As I downloaded BMS, after installing it was not such a file in my given location.
The file will only be created after you used the “.gvd” / “.guidedviewdump” commands in the chatline.
-
Hello Dunc,
Tried out what you said and I can use .gvd fine, but I don’t know where to put it on my 3dckpit.dat file. I tried guidedview 0 and guidedview 1 but I’ve not noticed any change… are these accessed via the “1” and “2” keys?
I’ve edited the .dat files for the block 50, 52, and 52+ on the ckptart folder, do I have to edit the ckptartn folder as well?
-
Er, nevermind. Turns out I was editing the C-version .dat files but I was testing with the training TEs which had the D-version F-16s. Duh! :uham:
-
LMAO!!!
RAM22
-
This post is deleted! -
@Dunc. Thanks for the tip.
I couldn’t use “.gvd” because I couldn’t find the “.” don’t laugh I have a French keyboard and maybe there is another issue as “, : ;” were located where they should be.
Anyway I edited manually and approx and already it is a major improvement. With 3 screens when it was 59.999… I added 60 to 119.999… and same for 31… or 34: I added 60 so it is 91…etc
The only pity is to have to redo all of that (even with the find and replace function) for all the cockpits I use for the day and for the night… -
I have edited my 3dckpit.dat file in Data\Art\ckptartn folder, and also in the F-16D-52; F-16C-50 and F-16C-52 folders. When I fly any of those planes I see no changes… My view is always locked zoomed in. :mad:
I have a 3 monitor setup as well. What am I missing here?
[i]//Guided snap views //Center // ORIGINAL: guidedview 0 0.000000 0.000000 0.000000 -0.000000 1.791412 0.000002 59.999996 0 23 9000 29 18000 1 27000 26 'HUD - up once' // SAMPLE: guidedview 0 0.000000 0.000000 0.000000 0.000000 -13.887756 -0.000000 139.999985 <ndir> <nid> '' guidedview 0 0.000000 0.000000 0.000000 0.000000 -13.887756 -0.000000 139.999985 0 23 9000 29 18000 1 27000 26 'HUD - up once'[/i]</nid></ndir>The ‘SAMPLE’ is the line generated in the dump and I copied that to the line indicated in this post. But there is no change. My FOV is way zoomed in because of my wide resolution.
-
Just a NOTE:
There is also a folder called: Data\Art\ckptartn
DON’T use that folder!
-
ckptartn is for the night…
-
Thanks, that is good to know I should edit both.
-
I have edited my 3dckpit.dat file in Data\Art\ckptart folder, and also in the F-16D-52; F-16C-50 and F-16C-52 folders.
Just so that I found it back easily
it is important to apply same changes "to the 3dckpit.dat in ckptart folder (not only the one in the F-16CM-50 folder etc.) and as well to 3dckpit.dat in ckptartn and the specific folders for night use.With my triple screen 5880x1080 I use 119.9999 for the values to be changed.
In config file I have: set g_fMaximumFOV 180
set g_fFOVIncrement 10
set g_fDefaultFOV 150
Best settings in my opinion particularly in 3D surround -
Just so that I found it back easily
it is important to apply same changes "to the 3dckpit.dat in ckptart folder (not only the one in the F-16CM-50 folder etc.) and as well to 3dckpit.dat in ckptartn and the specific folders for night use.With my triple screen 5880x1080 I use 119.9999 for the values to be changed.
In config file I have: set g_fMaximumFOV 180
set g_fFOVIncrement 10
set g_fDefaultFOV 150
Best settings in my opinion particularly in 3D surroundHi ! I have a question about this, I set den DefaultFOV in .cfg but if i start it is zoomed in?
Now i change it in all important f16´s .dat but it doesnt work…
Greetings !
-
I found it : if i disable mousewheel axis in fov(setup ingame) it works fine. This mouse still have the function…
