festr

same problem on VARJO XR4

I have reported similar issue (reproducible) https://discord.com/channels/542985647502393346/1316771017632383049 with detailed .miz and backtraces when it freezes. I have edited .miz -> mission.lua and set all uncontrolled = true to uncontrolled = false and this caused mine test scenario to not freeze anymore.

Its "Process Explorer" once it happens just find the DCS.exe and you can show all threads - and do the trace for the first two which takes the most CPU

please check my bug report - https://discord.com/channels/542985647502393346/1316771017632383049 if you have similar symptoms I can reproduce the hang

changing resolution fo the focus area changes nothing - it still behaves differently - shows different lightening compared to the outer. It looks like the same rendering is not applied to all quad views.

In the latest dcs update I can now see texture brightnes in the focus area differently compared to the outer area. It is like focus area sets higher brightness which si very distracting making the whole focus area box visible. If I turn off shadows it is less visible but with shadows the brightness difference is bigger.

it is still bad when I'm in VR and moving mouse with polling rate 1000hz - the cpu impact is nonsensically high

Hello, We are announcing a new PVP campaign that will run every Thursday starting October 10th, from 20:00 to 23:00 (GMT+1, Prague). Based on the Coop engine Map: Syria Scenario 90s (Amraam 120B, JDAMS, HARMS) Every Thursday 20:00 (GMT+1 Prague) - till 23:00 - the progress will be preserved for next rounds. The goal is to establish a stable group of players who enjoy organized battles where only teamwork can lead to victory. Each team can prepare during the week and showcase their best coordination. You can bring your entire flight group—one advantage being that your group will be assigned specific tasks based on the team's current needs. If you join solo, you'll be assigned to a flight group. The idea is to make a plan each week, with autonomous flight groups working together to achieve team objectives. If you're interested, please sign up on this sheet: https://docs.google.com/spreadsheets/d/1Tkq62Y6RpPd1AFzKTuo7nFTws3PS_EF2xkovJhhNqOw/edit?usp=sharing We are currently addressing a major design decision. Our ideal scenario is that RED airframes will not include any blue fighters like the F16. Therefore, the first step in recruiting players for this campaign is to survey how many RED players are willing to play using only JF-17, F-14, Mig, SU, or similar aircraft. If we don't have enough RED players, the F16 may be considered for the RED Team or Our flight group can start as RED supporting with JF17. Feel free to discuss this in weekly-chat (keeping discussions brief—simply indicate if you would be willing to play for RED if the F16 is included on the RED side) or signup to the online sheet straight away. https://discord.com/channels/995756259691221072/1291380838034051143 https://discord.gg/ua7JGmV95S

Mbuchas DFR is crucial for XR4 headset which has 4k panels for each eye. There is tuning option which allows to lower the peripheral resolution - I personally use 0.6 scale factor of the peripheral alongside with DLSS which still looks nice (almost indistinguishable from the scale 1) and it saves a lot of FPS. I can also make the focus area larger to my liking. There is also "turbo mode" switch which smoothness FPS if you reach maximum possible for the headset (less stutters). The tuning option like scaling of the resolution and scaling the focus area is crucial and this should be possible to define directly as a new DCS internal options before we can fully drop mbuchas DFR.

on varjo discord another user with aero reported that it works for him like before the patch. Did you enabled the quad rendering in the new DCS option in the VR section? (I have XR4)

turning off the eye tracking in the new vr option fixed the problem with wonky center area. mbucha extension is also working but the quad rendering MUST be enabled in the DCS and eye tracking MUST BE DISABLED all is working as expected - the only problem for varjo seems to be that the eye tracking has to disabled

I have managed to debug the foveated rendering - the rectangle in DCS is too small - we need to have control over this in DCS - to be able to change the rectangle size + possibility to change the resolution scaling of the rendering in the inner and outer - otherwise its huge step backwards. there is also glitch when looking left the rectangle changes like this on the picture and I can see artefact on the whole image if this happens: null

I can confirm. FDR Mbuccia stopped working. Following the recommended varjo enabling foveated rendering (without the mbucha) enables the foveated rendering but the eye tracking does not work.

DCS crashes when groupData does not contains name (or x / y ) - once I add groupData.name and x / y (not sure if it is due to missing group position or just the name). . Test mission .miz is also attached here which reproduces the crash -- Define the group structure local groupData = { ["visible"] = false, ["lateActivation"] = true, ["tasks"] = {}, -- end of ["tasks"] ["uncontrollable"] = false, ["task"] = "Ground Nothing", ["hiddenOnMFD"] = true, ["taskSelected"] = true, ["route"] = { ["spans"] = {}, -- end of ["spans"] ["points"] = { [1] = { ["alt"] = 5, ["type"] = "Turning Point", ["ETA"] = 0, ["alt_type"] = "BARO", ["formation_template"] = "", ["y"] = 544035.72022567, ["x"] = -495526.32864228, ["ETA_locked"] = true, ["speed"] = 0, ["action"] = "Off Road", ["task"] = { ["id"] = "ComboTask", ["params"] = { ["tasks"] = { [1] = { ["number"] = 1, ["auto"] = false, ["id"] = "WrappedAction", ["enabled"] = true, ["params"] = { ["action"] = { ["id"] = "Option", ["params"] = { ["value"] = 2, ["name"] = 9, }, -- end of ["params"] }, -- end of ["action"] }, -- end of ["params"] }, -- end of [1] [2] = { ["enabled"] = true, ["auto"] = false, ["id"] = "WrappedAction", ["number"] = 2, ["params"] = { ["action"] = { ["id"] = "Option", ["params"] = { ["value"] = false, ["name"] = 20, }, -- end of ["params"] }, -- end of ["action"] }, -- end of ["params"] }, -- end of [2] [3] = { ["enabled"] = true, ["auto"] = false, ["id"] = "WrappedAction", ["number"] = 3, ["params"] = { ["action"] = { ["id"] = "Option", ["params"] = { ["name"] = 24, ["value"] = 32, }, -- end of ["params"] }, -- end of ["action"] }, -- end of ["params"] }, -- end of [3] }, -- end of ["tasks"] }, -- end of ["params"] }, -- end of ["task"] ["speed_locked"] = true, }, -- end of [1] }, -- end of ["points"] ["routeRelativeTOT"] = true, }, -- end of ["route"] ["groupId"] = 11785, ["hidden"] = false, ["units"] = { [1] = { ["skill"] = "Excellent", ["coldAtStart"] = false, ["type"] = "Patriot cp", ["unitId"] = 19583, ["y"] = 544035.72022567, ["x"] = -495526.32864228, ["name"] = "BLR-16", ["heading"] = 3.1415926535898, ["playerCanDrive"] = false, }, -- end of [1] }, } -- Function to spawn the group at the start of the mission local function spawnGroup() groupData["lateActivation"] = false coalition.addGroup(country.id.USA, Group.Category.GROUND, groupData) trigger.action.outText("Group spawned: BLR-16", 10) end -- Schedule the group spawn function to run at the start of the mission timer.scheduleFunction(spawnGroup, {}, timer.getTime() + 1) crash.miz

we are seeing strange issues on multiplayer servers where aim120b are passing through m2000c planes like the missile is not seeing the mirage at all. Confirmed multiple times on my own eyes as a jtac - and those pilots in mirage are not even evading those missiles so they know it will not track them - unfortunately the server does not export data so there is no prove. Thats why I was curious if this is a still problem - at least for aim120B