phrogZ

Thx ED !!! hope to see more API improvement like that in the future

Hello, I not 100% it's the last patch that change something, and I'm not 100% sure that is not the normal behaviour. With the world.event.S_EVENT_DEAD event, it seems there are more empty events (with only ["id"] and ["time"]). And some other dead Events are coming about 1 minute later, some are coming live. I added a simple mission as a POC. Test_3_DeadEventSimple.miz

What you did to have persistence is awesome. If you do the ratio of benefits/problems... benefits win largely . IMO It was worse few years ago, and now it's pretty reliable! Speedboat issue ( It was not already reported, and I have this issue since 3-4 months ago) will be fixed. It's not a blocking point, you can still open the editor and remove the unit. I also had the second case it happens approximately on 1 of 50 killed unit, not a big deal, kill again the unit a second time and voila!

For the speedboat I'll ask today, but I want to submit an other issue a the same time (I need to build a short miz to reproduce the other problem).

It's has been reported internally, and a fix is coming... I encounter the issue with some static unit (I.E. sandbox) and not all the static unit. There was also an issue with the speedboats that are not saved with the persistence, BUT it's not specific to this update ( I didn't troubleshoot it, neither reported it).

There is a bug. The problem has been reported last week, and it seems there is a fix ongoing .

With the last two patches, does someone saw some strange behaviour with the persistence file and static unit? In SnowfoxUnitInterment.lua, there are entries like SnowfoxUnitInterment[28] = "static" It happens when a static unit is destoyed, normally it shoud go in SnowfoxStaticInterment.lua but it's not. Did I break something, or is it the latest patch?

Hello, this sounds awesome. I have few questions about moving units and how the "load/save part" is working: 1/ In case of unit (naval/ground), when there are loaded do they spawn in there original location? I.E. If they are moving, does they spawn at there original location? or the position is saved and they will spawn to there last saved location ? 2/ If there is a moving unit, what happens after the "next load" do the waypoints are still here?

I don't know if it has been already suggested, but as far as I remember the pilot and name should be exactly the same.

In i10n\DEFAULT\ look at the file named "something Helo Operations.lua" it should be in the function "function EventHandlerHeloBirth:onEvent(Event)", or just search the line if ( EventGroupType == "UH-1H" or EventGroupType == "Mi-8MT" or EventGroupType == "SA342L" or EventGroupType == "SA342M" or EventGroupType == "SA342Minigun" or EventGroupType == "SA342Mistral" or EventGroupType == "Ka-50" or EventGroupType == "Mi-24P" or EventGroupType == "AH-64D_BLK_II" ) then I guess if you add the getTypeName() of the UH-60L, it should work. Not sure but to give you an idea (I'm unsure of the typeName) : if ( EventGroupType == "UH-1H" or EventGroupType == "Mi-8MT" or EventGroupType == "SA342L" or EventGroupType == "SA342M" or EventGroupType == "SA342Minigun" or EventGroupType == "SA342Mistral" or EventGroupType == "Ka-50" or EventGroupType == "Mi-24P" or EventGroupType == "AH-64D_BLK_II" or EventGroupType == "UH-60L" ) then

Issue fixed, Thx a lot!!

cool, many thanks for the feedback!

Thanks, two d3dx_user.ini file from my computer and my laptop. I added the d3d11_log.txt from my computer (from the test with a new dcs profile). Laptop_d3dx_user.ini NormalPC_d3dx_user.ini NormalPC_d3d11_log.txt

So I updated the result in the previous post above. But I tested on my laptop (new DCS setup + new quest 2 setup + windows 11) and I have the same result. I attached the logs if needed, and It was test during a quick free flight with F-18. nvapi_log.txt d3d11_log.txt

Thanks for the feedback! I have the issue on any mission (solo and multiplayer), It seems to be particular to my setup. So I'm not sure a track will be useful for you. I plan to do more testing soon: If possible test running the launcher in "windows 10" compatibility mode. Test with a new dcs profile: KO Test on another computer: KO Try to disable some overlay (microsoft gamebar and or nvdia stuff): No overlays enabled Is there any other test I can do?

no, and it's on an other disk: "D:\Eagle Dynamics\DCS World OpenBeta" I just tried to launch the loader as an admin, same issue. I tried also solo, same issue. Are you running windows 11 ? This can be my problem...

I just tried lcontrol + lalt + f12. It doesn't solve the issue. I discovered that lalt+f12, reset something because after that I can access to the lshift+f7 menu again. Now I'm able to fully describe the problem (with screenshot): 1/ in the map screen (F10) I press lshift+f3 2/ I press F1 to return in the cockpit, and no coordinates are displayed. 3/ If I press lshift+f7 I have this: 4/ Then if I press lalt+f12 (OR lshift+f7 to close the upper left "square" and lalt+f12), I guess it's reseting something because I can then access the lshift+f7 menu. Here are my video settings, I think there are compliant with the mod:

Without any other mods with a full check/repair, I've the same (with a quest2). Shift+f7 is displaying the menu, then after saving the config the mod doesn't work anymore (shift+f7 KO and shift+f3 KO).

Ok, thanks for the feedback! Seems to be on my side, I'll do more troubleshooting... Starting by a full repair, and the troubleshotting guide.

It seems the mod isn't working with the last version (it wasn't with the previous beta too). When I launch the game and join a server I can go in the shift+f7 menu once, save the settings. Then nothing works shift+f3 or shift+f7. In the logs (see attached) there are the following errors: "failed result = 80004002 for 00000041F04FEF78" I'm using: 3DmigotoDCS_VR_16.4_openXR And I tried too repair and remove/install the mod, without any improvement. Thanks for your work, this mod is a must have for VR! d3d11_log.txt

+1 Interoperability should be considered too...

+1

Many thx, btw verbose is on

+1