Jump to content

JUICE-AWG

Members
  • Posts

    579
  • Joined

  • Last visited

Posts posted by JUICE-AWG

  1. @upyr1 Looks like you're getting it!  AWG hopes to provide more info on this when we can...until then, look for an ED FAQ when we get an update!

    Thanks for leading this charge!

    Juice

    CW_HOT.jpg

    On 4/6/2023 at 10:51 AM, bies said:

    Yes, Cold War Germany map is arguably the most anticipated one together with Vietnam. But personally i think just one e.g. ~1970s would be ok. Changes in a decade were not that big, especially from flight simulator perspective. I would guess somewhere around 1960s all main NATO bases in Germany were already developed and functional, Berlin wall built. Civilian infrastructure developed obviously. Maybe two versions 1950s and 1980s at most.

    Germany 2023 vs. 1970s are massively different and it would be huge turn off for all this Cold War scenarios, but 1960s vs. 1980s would be ok.

    map-de-fulda-gap-3.webp

    I believe early 80s would be best!  I have the soundtrack for that already...Cheers!

    • Like 2
  2. I noticed this issue right away with the installation of WW MIP w/Screens this week.  Win11, everything updated and current.  One correlation I have noticed, the screens hold orientation if I put the PC in hibernate mode and not a full reboot/shutdown.  I think it's a Windows issue how it reads USB HDMI connections.  I have now moved those three 3.1 HDMI USB lines directly to 3.1 slots on the motherboard.  Everything else is powered USB hub.  I have a direct line with WW and am reporting this daily.  Hope for a solution soon!

  3. On 4/14/2024 at 11:17 PM, draconus said:

    Well OK, but why "by Razbam" (very unpopular atm) and why only "model" (3D gfx model)? We ask for the whole FF DCS module here :thumbup:

    Sorry, I was inferring Full FIdelity!  Friends don't let friends fly FC3? 

  4. UPDATE: 2024

    So, this issue is apparently tied to the Mission Editor settings on view options I enforced on certain missions to make them more difficult.  Default DCS Instant Action missions save the settings as I desired, but some, not all, of my custom missions are causing it to revert.

    HOWEVER, If I spawn in on the affected mission, and leave immediately, I can go back to one of the ED-provided default missions and it works fine.

    I sent this information to @[ED]Ben earlier in the week.  I'm sure they will discover what is causing it soon.  Thanks all for the help!
     

     

    • Thanks 1
  5. On 1/1/2024 at 8:41 AM, Ornithopter said:

    The problem has been explained over and over again, and I really don't know how to explain it further.  The new 'viewAngleVertical' parameter screwed up the existing Snapviews, and apparently the only way to restore the custom default views, are to do them over again, completely from scratch.  That's a lot of time.  I just want my existing default cockpit view back.  And Yes, that new parameter should have populated automatically, based on the existing value for horizontal field of view.  I assume that value should be proportional to screen aspect ratio.

    So I either need to go in and populate them manually in the Snapview.lua, or I have to load up every single aircraft and try to recreate what I had, and hit Alt Num0.

     

    I didn't even know there was a "FOV slider" now in the settings....How long has that been there?  hmm. In fact I don't even know what your talking about.   edit:  Duh, I call those "Zoom In" and "Zoom Out", and didn't know what you meant when you said "FOV slider", disregard.

        [13] = {--default view
            viewAngle        = 110.200706,--FOV
            viewAngleVertical= 61.932899,--VFOV
            hAngle            = 0.000000,
            vAngle            = -9.500000,
            x_trans            = 0.113927,
            y_trans            = -0.004946,
            z_trans            = 0.000000,
            rollAngle        = 0.000000,
            cockpit_version    = 0,

    So, here are my results doing the same...  Like I said, I have a 21:9 aspect ratio.  So 110 degrees across, and 62 degrees high?  Funny that it gives me degree proportions for a 16:9 monitor.  Guess I'll just have to stick in the correct value for all planes, like 47 deg because that would be the correct proportions for 21:9.  But honestly, I'm not even sure the parameter is being used.  I'll have to just look and see if it even matters.

    UPDATE:  Changing that viewAngleVertical to reflect a 21:9 aspect ratio didn't give me the results I expected.  Therefore, I'm just going to let the calculated value of 61.9 deg stand as is.  Those dimensions don't quite make sense, but nothing ends up being visually squished, and I am able to recreate my old default cockpit views more or less, so those dimensions are the ones I'm going to use.  Pasting it in to every section [13] for every airplane is a pain, but not even close to as time consuming as it would be to load up all the planes and redoing all the angles and zooms from scratch with the view controls and Alt Num0! 

    It would have been a lot more convenient if the existing Snapview.lua had been updated automatically to reflect the new parameter, without requiring any action on the customer part to retain their existing custom view angles and zoom. 

     

     

    Are you able to connect on Voice and I can screen share with you?  I'm wondering if we could work out my settings in the lua on one aircraft as a customizable option.  I have set the settings in the slider and using the zoom in/zoom out functions on the number pad (* and /) and confirmed everything is mapped.  I have the "zoom normal" mapped to NUMPAD Enter and I have "Save Cockpit Angles" mapped default to the right ALT NUMPAD 0 key and it works.  

    The one think that is working as advertised is the external FOV slider in SYSTEM tab is set to 78 degrees and it stays there for all aircraft no matter what.  for my 16.9 monitor and from my experience sitting in many of these cockpits for real, I get the best balance of internal distance from things and external view of the world on a 1:1 ratio to avoid that convexed fisheye effect that the default settings do.

    Did you see my very first FOV video from years ago?
     

     

  6. 12 hours ago, SharpeXB said:

    Can’t say I’ve seen that happen yet. I’ve done this on the ones I use currently; the F-18, A-10CII, M-2000C, P-47, F-15E, AH-64 and Spitfire 

    Something is affecting it for me...perhaps running Replay Tracks?  But two days ago I set up P-51, F-16, AH-64, and F/A-18 just perfect and it worked for a day...then the next day, back to defaults like 100 FOV or 109 in the Hornet.  I didn't make any changes, no lua edits, no additions or deletions.

    I do use Track Replay, do you use it or have you tried it to see if it affects anything.

    QUESTION: Since this seems to be tied with SnapViews is there a command like the "ZoomNormal" that is to load your Snap Views Saved profile or something?

    I am also not using the Zoom on a slider...disabled as I don't use artificial Zoom in Cockpit.

    J

    On 1/21/2024 at 7:08 PM, SharpeXB said:

    This worked on all the aircraft I’ve tried it with. 

    Yes, it works with all aircraft I tried it with, but if you set another aircraft up, does it kill the setting for a previous aircraft you set up.  I feel ED screwed this up when they tried to make FOV a one-size fits all slider on the options page.

    J

  7. On 1/17/2024 at 5:17 PM, SharpeXB said:

    Try this:

    Go to C:\Users\Youname\Saved Games\DCS\Config\View and delete (or move out) the SnapViews.lua

    Launch DCS with head tracking Off unless you want that input captured.

    Make sure User Snap-View Saving is checked under Options/ Misc. You need this enabled to either create or use the custom FOV setting.

    Launch an Instant Action Mission like Cold Start and using that initial cockpit view, set it up the way you like. If you hit Esc while in this view and go to Options, you'll see the FOV slider now says "Internal" FOV and you can dial it in with that.

    Press RAlt+Num0 (Save cockpit View Angles) and exit. (This creates a new SnapViews.lua)

    Reload the aircraft and this should have set your initial FOV as well as Zoom Normal

    That sets this value in the new SnapViews.lua

    [13] = {--default view
            viewAngle        = 95.000000,--FOV
            viewAngleVertical= 63.088276,--VFOV
            hAngle            = 0.000000,
            vAngle            = -15.700000,
            x_trans            = 0.130000,
            y_trans            = -0.008300,
            z_trans            = 0.000000,
            rollAngle        = 0.000000,
            cockpit_version    = 0,

    That fixed it for me in both Stable and OB

    @SharpeXB Do you know if this will apply the adjustments to every aircraft and have we lost the ability to customize and save settings for each aircraft like we had in the past?

    Feel free to message me on Discord...I'm a mature (old) guy like you!

    juice_awg on Discord

  8. On 1/17/2024 at 5:17 PM, SharpeXB said:

    Try this:

    Go to C:\Users\Youname\Saved Games\DCS\Config\View and delete (or move out) the SnapViews.lua

    Launch DCS with head tracking Off unless you want that input captured.

    Make sure User Snap-View Saving is checked under Options/ Misc. You need this enabled to either create or use the custom FOV setting.

    Launch an Instant Action Mission like Cold Start and using that initial cockpit view, set it up the way you like. If you hit Esc while in this view and go to Options, you'll see the FOV slider now says "Internal" FOV and you can dial it in with that.

    Press RAlt+Num0 (Save cockpit View Angles) and exit. (This creates a new SnapViews.lua)

    Reload the aircraft and this should have set your initial FOV as well as Zoom Normal

    That sets this value in the new SnapViews.lua

    [13] = {--default view
            viewAngle        = 95.000000,--FOV
            viewAngleVertical= 63.088276,--VFOV
            hAngle            = 0.000000,
            vAngle            = -15.700000,
            x_trans            = 0.130000,
            y_trans            = -0.008300,
            z_trans            = 0.000000,
            rollAngle        = 0.000000,
            cockpit_version    = 0,

    That fixed it for me in both Stable and OB

    Thanks, I'll give it a try!

  9. On 12/13/2022 at 9:38 AM, Hiob said:

    My pleasure!

    My User Snap View Save was checked before and still checked now and doesn't affect the saving function...still broken.

    I have noticed the issue might be related to switching aircraft with different settings.  The External FOV slider that was introduced within the past year, sets the default FOV for outside for all aircraft, but perhaps setting the inside FOV (which is optimally different inside each aircraft) shouldn't be saving my Hornet inside settings for my Mustang inside settings.  The Depth Of Field and distances are different.

    There is actually three (maybe a fourth) dimensions to consider when dialing in the inside/outside world for each aircraft.

    1-Outside FOV

    2-Inside FOV

    3-HUD Information Stretch

    4-HMD/IHADS Information Stretch

    I'll do a video to demonstrate.

     

    On 12/13/2022 at 9:24 AM, SharpeXB said:

    I’ll try the A-10CII although they all behave the same way. If I go with the default, no modified files. Num0 produces a view angle of 73.0

    if I adjust this to say 111.4 and press RAlt+Num0, and change the zoom, pressing Num0 returns me to 111.4. So far so good. 
    Quit DCS and go look at my files. 

    C:\Users\Myname\Saved Games\DCS\Config\View

    there is now saved a file SnapViews.lua

    Opening this reveals

    SnapViews["A-10C_2"] = {
    [1] = {-- player slot 1
        [1] = {--LWin + Num0 : Snap View 0
            viewAngle        = 65.000000,--FOV
            hAngle            = 0.000000,
            vAngle            = -26.000000,
            x_trans            = -0.050000,
            y_trans            = 0.000000,
            z_trans            = 0.000000,
            rollAngle        = 0.000000,
            cockpit_version    = 1,
        },
        [2] = {--LWin + Num1 : Snap View 1
            viewAngle        = 50.000000,--FOV
            hAngle            = 0.000000,
            vAngle            = -90.000000,
            x_trans            = 0.282000,
            y_trans            = -0.100000,
            z_trans            = -0.250000,
            rollAngle        = 0.000000,
            cockpit_version    = 1,
        },
        [3] = {--LWin + Num2 : Snap View 2
            viewAngle        = 31.000000,--FOV
            hAngle            = 0.000000,
            vAngle            = -90.000000,
            x_trans            = 0.494000,
            y_trans            = -0.055000,
            z_trans            = 0.250000,
            rollAngle        = 0.000000,
            cockpit_version    = 1,
        },
        [4] = {--LWin + Num3 : Snap View 3
            viewAngle        = 55.000000,--FOV
            hAngle            = 0.000000,
            vAngle            = -90.000000,
            x_trans            = 0.261000,
            y_trans            = -0.065000,
            z_trans            = 0.250000,
            rollAngle        = 0.000000,
            cockpit_version    = 1,
        },
        [5] = {--LWin + Num4 : Snap View 4
            viewAngle        = 35.000000,--FOV
            hAngle            = 0.000000,
            vAngle            = -10.000000,
            x_trans            = 0.238000,
            y_trans            = -0.281000,
            z_trans            = -0.231000,
            rollAngle        = 0.000000,
            cockpit_version    = 1,
        },
        [6] = {--LWin + Num5 : Snap View 5
            viewAngle        = 52.000000,--FOV
            hAngle            = 0.000000,
            vAngle            = -9.500000,
            x_trans            = 0.323000,
            y_trans            = -0.053000,
            z_trans            = 0.000000,
            rollAngle        = 0.000000,
            cockpit_version    = 1,
        },
        [7] = {--LWin + Num6 : Snap View 6
            viewAngle        = 35.000000,--FOV
            hAngle            = 0.000000,
            vAngle            = -10.000000,
            x_trans            = 0.238000,
            y_trans            = -0.281000,
            z_trans            = 0.231000,
            rollAngle        = 0.000000,
            cockpit_version    = 1,
        },
        [8] = {--LWin + Num7 : Snap View 7
            viewAngle        = 68.628296,--FOV
            hAngle            = 68.292320,
            vAngle            = -11.477349,
            x_trans            = 0.000000,
            y_trans            = 0.000000,
            z_trans            = 0.000000,
            rollAngle        = 0.000000,
            cockpit_version    = 1,
        },
        [9] = {--LWin + Num8 : Snap View 8
            viewAngle        = 68.628296,--FOV
            hAngle            = 0.000000,
            vAngle            = 30.227919,
            x_trans            = 0.000000,
            y_trans            = 0.000000,
            z_trans            = 0.000000,
            rollAngle        = 0.000000,
            cockpit_version    = 1,
        },
        [10] = {--LWin + Num9 : Snap View 9
            viewAngle        = 68.628296,--FOV
            hAngle            = -67.172974,
            vAngle            = -11.477349,
            x_trans            = 0.000000,
            y_trans            = 0.000000,
            z_trans            = 0.000000,
            rollAngle        = 0.000000,
            cockpit_version    = 1,
        },
        [11] = {--look at left  mirror
            viewAngle        = 73.000000,--FOV
            hAngle            = 5.888000,
            vAngle            = -2.468000,
            x_trans            = 0.238000,
            y_trans            = 0.100000,
            z_trans            = -0.114000,
            rollAngle        = -22.000000,
            cockpit_version    = 1,
        },
        [12] = {--look at right mirror
            viewAngle        = 73.000000,--FOV
            hAngle            = -5.888000,
            vAngle            = -2.468000,
            x_trans            = 0.238000,
            y_trans            = 0.100000,
            z_trans            = 0.114000,
            rollAngle        = 22.000000,
            cockpit_version    = 1,
        },
        [13] = {--default view
            viewAngle        = 111.384400,--FOV
            hAngle            = 0.000000,
            vAngle            = -19.000000,
            x_trans            = 0.150000,
            y_trans            = 0.000000,
            z_trans            = 0.000000,
            rollAngle        = 0.000000,
            cockpit_version    = 1,
        },
        [14] = {--default view - VR
            viewAngle        = 73.000000,--FOV
            hAngle            = 0.000000,
            vAngle            = -19.000000,
            x_trans            = 0.150000,
            y_trans            = 0.000000,
            z_trans            = 0.000000,
            rollAngle        = 0.000000,
            cockpit_version    = 1,
        },
    },
    }

     

    aha there's my number

     

    IF you could, now go and change another aircraft FOV (Not SnapView Setting everyone) and then save it, exit and return and check both LUAs.  Let me know what you notice.  Thanks!

  10. On 1/1/2024 at 12:23 PM, Ornithopter said:

    The only slider I see on the Options page is labelled "External Field of View".  I can't find any others (although I might be blind). Its been a long time since I manipulated my views, like years, so whenever that was added I didn't notice.  I had played around with it earlier today, and it seemed only to influence the F2, externals, so if there is more to it, that is good to know.  I'll have to mess around with it.  If that slider works to set a particular value in the Snapview.lua, that will be good for future aircraft.  I guess, for existing aircraft with existing custom views, one would still have to load up every aircraft, and Save the view again, but at any rate, it looks like I've got it all sorted out, after lots of cutting and pasting, lol.  Thanks, SharpeXB.

    Thanks for your input...According to the DCS User Manual for the base program, the SnapView is a momentary look at a particular part of the cockpit, panel, or screen when programmed to the key/combo commands you choose.  The Cockpit Angles and Zoom Normal functions should be separate of SnapViews and it seems like a lot of people are grouping the subjects together as one, when in my research, they are different parameters.  I've edited the Lua and used the sliders, and used the old way of zooming to a desired level and Right Alt + NumPad Zero and still doesn't save or recall it after leaving the cockpit or game.  I do hope a clear solution is found someday.

    • Like 1
  11. On 12/31/2023 at 7:23 AM, Flappie said:

    Thank you.

    Well, I've just tried it and it works fine in OB (2.9.2.49940), even after a DCS restart, which means my custom FOV was saved in SnapViews.lua successfully.

    Are you running DCS as an administrator?

    I am running as Administrator, MT, 2.9XXX and still not saving once leaving the aircraft or game.  As of last night, still broken!

  12. On 12/10/2022 at 7:32 PM, SharpeXB said:

    I assume that save cockpit angles RAlt+Num0 is supposed to save your normal zoom level in the cockpit. This seems to work but after exiting the game the “normal” zoom level returns to this crazy zoomed-in view. 
    I see the snapview.lua file that’s created in my Saved Games files and the zoom value I’ve set there. I think the game just overwrites this when it’s restarted. 

     

    THIS IS STILL HAPPENING TO ME!

    @BIGNEWY Snap Views and Cockpit Angles/Zoom Normal should be separate things.

  13. @corbu1 I'm addressing that with Guitammer and ED in a few days, I just got mine a week ago and going through the various aircraft to see what is missing and nonfunctional.  You are correct, it's not optimized for helicopters yet.

    @Cobra_B39 Honestly, from all the racing sim guys that reviewed it, I agree...settings depends on your rig, how heavy it is, and where the device is attached.  What works for others might not be the best settings for you.  That's why each setting starts out default in the middle.

    Did anyone have issues getting CHAFF and WINGFOLD to register in the Hornet?  Everything else responds and FLARES work fine.

    J

×
×
  • Create New...