Draken35

Absolutely correct! I use a Quest 3 and have no issue with the visor but the where the center of any JHMCS is too high for me. With the amount of possible different combinations of headsets, single and multiple monitors and particular user settings and resolutions out there, a "one size" kind of approach will never "fit all". Of course, that same combinations of hardware and software setting make the generalization of comments like "it doesn't work well for VR" (just an example, since I fly only in VR) absurd. What doesn't work well from one user might be perfect for others. Options about configuring these features is what we all need. It is definitely a challenge for the dev team.

Historical filter on

Ah! I see what you mean.. Never thought of testing the existence of a method that way... Gotta test that later And that was a weird error... I can see an initiator not existing when hit event triggers (long range weapon and initiator destroyed before it reaches the target) but since the initiator should be an unit, it has to have the method... Anyway, it would be interesting to dump the whole initiator object to the log to see what it is in there.

Ohhhh! This was for Polar Shield? Thanks for the campaign! It is my queue to fly it

My pleasure! You are missing a () after the getName in the and. Also, what was the error you were getting? That initiator did not had a getName() function?

What error do you exactly get? Hit event initiators should be an unit object with a getName(). It is been a while but if I recall correctly I got into a similar issue with Hit event detecting the initiator when the target was hit with the bomblets of cluster bombs. That will fail if initiator is nil you can use a pcall to test the getName() if event.target.getCoalition and event.initiator then local status, a= pcall(function(p) return p:getName() end,event.initiator) end if status is true, a has whatever getName returned. If status is false, a will have the error description

Best bet is to ask in their their discord and be prepared to share DCS logs... https://discord.gg/F7ZGzd54

As long as it is NOT named DCS you can give any name. The point of the test is that DCS do not find the old folder and creates a new one.

Enjoy you new eyes! Best procedure I ever had done!

Ah! Gotcha... I do too, same reason... Thanks!

Could you share the workaround please?

Thanks! Just a quick and dirty script to test a concept. Those settings are the localization settings added bu MOOSE. This script doesn’t use them.

Mission file finally approved: https://www.digitalcombatsimulator.com/en/files/3347231/

S_EVENT_HIT will tell you nothing about where the bomb hit unfortunately. Worse, by the time it triggers, the weapon object will not longer exists and you will be able to get any info about it. The strategy is to detect a drop with S_EVENT_SHOT and track its position with a scheduled function every 0.001 seconds , stop when the bomb is not longer alive and return the position... I don't have an example without using MIST or MOOSE but attached is one of my scripts with MOOSE . If you look under my user files, you will find some of my range scripts using MIST (they are a bit more complicated to setup_ sbsa.lua EDIT to add: This script depends on another (for TTS comms with the player). To use you will have to make the highlighted changes: I'll post an example mission to the user files and when it is approved, I'll link it in this thread

Any chance of adding BDU-33 or any other training bombs to the F1BE?

AWESOME! Thank you!!

Having native PAR would be awesome! But that, most likely, would be tie to the (new) ATC system

He's talking, I think, about SimShaker for Aviators Beta vs Stable

Awesome post! Thank you!

Let's see how this work: In all cases I was looking directly at the top of the tower 1.trk 2.trk 3.trk HMD Issue.miz

Ok. That assumes a cold and dark scenario and yes, you would be correct in that case it could be, easily user error... But in a hot start it would perfectly aligned so an incorrect alignment procedure wouldn't be a factor, right? I'll try to add a track / screenshot later today or tomorrow: Hot start, on the ground, looking at a well define object.

Honest question: Can you determine from a track file where the HMD is pointing to? Or where the center of the physical headset is pointing to? If so, we could setup a mission, look to a particular object (head level and object 'centered' in the line of vision ) so you can grab something useful from the track file. I think this has been done with screenshot, but if that helps you somehow, I can do it.

@BIGNEWY Sorry, I fail to see how a track would help here. This is the same Quest 3 too high issue that had been reported multiple times in the past 2 or 3 years with different modules that had a helmet mounted sight. Here are a couple of the threads: This is a physical headset issue that can be only solved by making the HMD adjustable in the special options of the respective module, like the BS3 has.

Since we now have user deployable RSBM / PRMG systems in the sim, can we have a deployable ILS? https://www.icao.tv/thales/videos/thales-atm-d-ils

Confirmed. Created new mission: Single (to rule out taxi interreference) veteran AI Harrier at Batumi, take of from parking, with a few waypoints including a landing one. Plane goes to runway, nozzles to 10° and seems to me adding power but moves only inches at the most. Seems to be stuck in the runway.