davidp57

Hi BigNewy, Any news from the team? Reshade works quite well, but in some conditions it's still a problem...

Ah, I missed the "mixed reality" part; I used to fly DCS in VR with a Quest3, and Reshade did not work in VR at the time. Thank you for the information!

I'll try and reproduce this in a simple single-player mission, for all my DCS experience is with multiplayer servers. But to answer your question, yes, I did the basic checks (laser code, etc.).

Hi, I've tested a few times to get the laser from a buddy (in an F16, with the Litening pod) or from a JTAC drone. It works well with the Litening, but I almost always fail to get a track with the Sniper. Do I miss something?

Hi, Is there a way to disable the feature that skips duplicate messages in the log file? I'm thinking that it's waiting for a new text to be logged before even logging the "XX duplicate message(s) skipped." message, making it difficult for us to check if some process is regularily logging the same message... @NineLine a thought? Thanks!

Nope, Reshade does not work in VR, unfortunately

btw the reshade tip is working great! Thank you for this!

Well, it's only been what? ... 6 years since we reported this already? A long time, anyway. Thanks for the tip on ReShade, I'll try this.

Merci Flappie !

Hi @BIGNEWY, here's a new bug report ! How to reproduce: In the mission editor, either set a "smoke" trigger command on a trigger zone, or use the `trigger.action.smoke` API command in script. What happens: The smoke effect starts, and a neutral ZIL-135 unit appears on the F10 map, which I can select and see coordinates of. It's a ghost unit though, there is no model in the 3D world, and the other units don't react to its presence. What I expected: I expected a smoke marker, nothing else. Screenshots: Here's a test mission: Testsmoke.miz

From the latest DCS update changelog: Let's hope that it solves our problems! Thank you @BIGNEWY

I think the problem will be exactly the same; in fact that's what I did in the beginning - and it didn't work (as described in my original post)

I've got a CTLD release incoming, with that feature implemented (and lots of others). Stay tuned !

Thank you @BIGNEWY! Just to give you some additional info, I added logging to my mission and, when running on a dedicated MP server, it goes like that:

Well, it's even worse than I thought. To work around this network sync problem, I've scheduled the resupply code to run each time a human spawns in the mission (using the S_EVENT_BIRTH event). Even with this ugly hack, it gives weird results. I set all the liquids in the warehouses to 5000kg + a random value between 1 and 100, and all the items to 50000 + a random value between 1 and 100. This is because if I don't use a random number, sometimes the warehouse does not get filled. Even there, I've got problems with people connecting and seeing weird things. Correct inventory, after logging in: Wrong inventory, after logging out and in again: This is so weird... Can someone help me please, this is a critical problem for BFR, their dynamic missions rely on spawning FARPs to unlock areas of the map. @BIGNEWY I don't know what to do, I could attach a trk but it's not going to be very useful.