F2 Outside View Goes Beneath The Surface of Ground

[Chopper A-10]

This may have been reported before, I was unable to find it . . . when using the F2 outside view and moving the mouse, your view goes under the ground surface.  Has done this for several updates for me.

 

A minor 'hiccup' in the overall improvements.

 

Thanks ED for your great product, keep up the outstanding work,

 

Chopper

[Flappie]

I could swear this happened to me a few days ago specifically with the Marianas, But I just can't reproduce this issue.

Can you please make a short track and attach it?

[Chopper A-10]

Flappie . . . this happens to me on all maps . . . this short track is from the Nevada Map.

 

I create all of my missions on my monitor, then fly them in VR . . . forgot if this is a VR issue also.

 

Thanks for quick response.

Ground Level Test .trk

[Flappie]

That's odd:

1. When I replay your track, I see what you see (camera goes underground),
2. When I trasform your track in a mission, I keep seeing what you see,
3. But then if I create my own mission with the same aircraft on the same airfield, I cannot reproduce the issue.

 

Either it's some mission parameter, or it's specific to VR.

F2_camera_test.trk

[Chopper A-10]

Wow . . . I took your track file, changed it to a miz and the ground issue is gone . . . this is in non-vr mode.

 

Our mission parameters show the same . . . 

 

Your created mission, no issues, mine all go underground.

 

Any ideas of other settings that I may have on that is creating this issue??  Thanks for the help Flappie

Edited July 5, 2021 by Chopper A-10

[Chopper A-10]

I thought I had found it, but, no . . didn't change anything.  Even created another mission with the updated settings. 

 

No change.

 

I found the setting was set to 'Floating' . . changed it to 'None'

 

The search continues . . . 

[Chopper A-10]

So I took my .trk file, changed the extension to          MBGround Level Test.miz     

 

And did the same to your .trk file                                 F2_camera_test.miz

 

I've attached the two files below.  Some where in the miz files is a different set of parameters . . . I've tried different maps, VR and non-VR . .  yours always works correctly, mine doesn't.

I've gone back my older missions, same thing. 

https://www.digitalcombatsimulator.com/en/files/filter/user-is-Chopper A-10/apply/

 

I don't believe it's a v2.7 issues, but I really don't know.  Way over my pay-grade.

 

I just updated my graphics card driver, no effect.  Will try a DCS Repair next.

 

 

If anyone has a suggestion on which file in the mission that I should look at and compare the two I'd appreciate it.

 

F2_camera_test .miz MBGround Level Test.miz

[Chopper A-10]

Flappie . .  I've looked thru the .lau files and I can't find a difference between the two .miz files . . . do you have any other ideas or may know someone that could look at this??

Thanks in advance for any help.  Chopper

[Flappie]

Sorry, I'm a bit busy at the moment.  I assume it has to do with some DCS custom setting. I'll take a look.

[Chopper A-10]

Thank you!

 

[Flappie]

I unzipped our respective tracks and I compared our settings (the "optons" file). Here are the most relevant:

 

Option = My setting - Your setting

 

["miscellaneous"]

["headmove"] = false - true

 

["difficulty"]

["setGlobal"] = false - true

["cockpitVisualRM"] = true - false

["padlock"] = false - true

 

["VR"]

["enable"] = false - true

["custom_IPD_enable"] = false - true

["box_mouse_cursor"] = true - false

["use_mouse"] = false - true

 

Maybe one of these settings prevent mouse view to go underground...

flappie_options.txt chopper_options.txt

Edited July 7, 2021 by Flappie

[Recoil16]

The issue lies in the miz in Config\View\Server.lua, line 6:

CameraTerrainRestriction 		= false

I assume the person who created the mission file modified their view settings to allow passing through ground (maybe to create cinematics), and that made its way into the mission. Deleting the entire Config folder from the miz should do the trick in order to get "normal" behavior consistent with your settings.

[Flappie]

Many thanks, @Recoil16!

[Chopper A-10]

Guys,

 

I renamed the Server.lua file from my F:/Eagle Dynamics/DCS World OpenBeta/Config/View folder and that worked.  Always worried about deleting files in ED.

New, old missions work great again.

 

I was trying awhile back to improve my video views and probably changed it listening to a Youtube video .. my bad.  Really don't remember doing it.

 

I ran a mission on the server and it worked fine, it hasn't recreated that file yet . . . if it needs it, ED will build it I'm sure.

 

ED has the best support group . . . thank guys for your efforts,

 

Chopper

[Flappie]

Thanks for your feedback.

[Recoil16]

11 hours ago, Chopper A-10 said:

I renamed the Server.lua file from my F:/Eagle Dynamics/DCS World OpenBeta/Config/View folder and that worked.

I just want to be clear that that is not what I recommended and that messing with files in the install directory is most certainly not recommended and can have unintended consequences.

[Chopper A-10]

Recoil16, not sure where or how to get at the Config/View folder you spoke of in the miz file . . . when I unzip the miz file, I don't see them.

 

I did run a "REPAIR" and the Server.lua file was created and everything is working.

 

I guess I don't understand were or how to access the Server.lua file you spoke of.

 

FYI, I'm just a dumb old 72 year old pilot that is trying to understand this tech stuff . . . thanks for any help you can provide,

 

Chopper

[Recoil16]

Oh, I see what's happening now. The miz file you attached in the previous post was converted from a track file, which is why it has the Config folder and the track data in it.

 

Nevermind then. Misunderstanding. If you ran a repair after deleting the Server.lua file and everything works you should be good now.

[Chopper A-10]

Thank you @Recoil16 and @Flappie