Draken35

It depends if you are in SP or MP. In MP, in the context where the LUA scratchpad script is running, it is possible to determine that the player is sitting in the WSO or CPG seats and the coordinates input will be done from whatever set the "load button" was pressed. Unfortunately, in SP that "role" is always Pilot, no matter in which seat you are, so the coordinates input will be done from the Pilot seat, even if you are seating in the other.

Right. ED unlocked "something" and the A-4 team was able to add AAR to their code that is in the DLLs.... Because they have full access to their source code and compile their DLL from it... Which, sadly, is not the case with the F-5E (Don't get me wrong, I wish I'm wrong, since I want AAR in the Tiger II, but chances are that I am not.) See StakeZIlla's remark above

I think you answered your own question... The A-4 is made from scratch and added the fuel transfer code to their systems model... That is probably inside a DLL and it is not LUA code.

No idea... It doesn't do that in my rig. I would suggest to make sure that there is no left overs of any prior install of any flavors of scratch pad in your setup, specially in the hooks folder.

Let's try again... READ THE README's (117) Updated! Go to:

I wonder if this is a reorg/clean up in preparation to the BE and M... Your work is appreciated!

Me! Only way to cancel the menu is with F12... Radio keys do not work for that like they used to

Nope, right forum! I don't know what you guys did with the MPCD in the Strike Eagle, but, please, do the same with the Harrier's! The Eagle's MPCD (heck, the whole cockpit!) looks fantastic in VR! Great Job!

@Bones478 Can you elaborate please? Which button are you talking about? I started experiencing this issue today, VR/MP. The other client was having it too. Sinai Map, heavy mission

There are several repeated parked spots numbers in this airbase (#100 show as example): 26,30,36, 50 & 100

Never mind ... Still happening

I just did a quick test with the latest OB and was unable to reproduce the issue. I noticed that the sight in the Gazelle is not retracted when bumped either. So I'm, yet again, sort of optimistic, but, can anybody else confirm please?

Thank you!

Off topic, sorry. Would you mind posting coordinates or a map of this valley please?

Don't take this the wrong, it is written in the internet and we don't know each other backgrounds or first languages...A bit about me: I'm a software engineer turned DBA with 35 years of IT experience, currently working for the Health Care industry. Never said that they did anything wrong, much less on purpose, but we live in dangerous times, from an IT perspective. If you want to assume that their (or ED's or yours) precautions are infallible, well, that is your choice , definitely, not mine. Yes, false positives do happen often, because of multiple reasons. One of those is that AV software try to "look into the future" as you said, because, we are at the defensive here... Hackers have the initiative. But, blindly (as in somebody, who we don't know or has official ties with with the files, posted in an internet forum that it is a false positive and can be ignore), ignoring them is not a good idea. I choose to "ignore" them because of my setup but it is not an advice I would give. The fact that is the same vendor (perhaps same IT infrastructure) makes it even more suspicious and I have not seen a comment from ED or the 3rd party, that the files are safe. Cheers

I am. I added the 2 files as exceptions (since this is a dedicated DCS machine and it is isolated of the rest of my network), and did a couple of slow repairs. I'm up and running but, these warnings cannot be lightly taken, plenty of bad stuff out there. I find it suspicions that the 2 files are from related (I think) 3rd party devs.

Bit Defender gave me these warning on my client PC and dedicated server: The file F:\Program Files\Eagle Dynamics\DCS World OpenBeta\CoreMods\aircraft\C-101\bin\C101Core.dll is infected with Gen:Suspicious.Cloud.4.gy4@a8i6Rsbi and was moved to quarantine. It is recommended that you run a System Scan to make sure your system is clean The file F:\Program Files\Eagle Dynamics\DCS World OpenBeta\CoreMods\aircraft\Mirage-F1\bin\MirageF1Core.dll is infected with Gen:Suspicious.Cloud.4.jy4@aelpIhbi and was moved to quarantine. It is recommended that you run a System Scan to make sure your system is clean

No Sir, Thank you! I have a very good idea of the time and effort that these "little" projects require, and you do really good work across multiple modules! Downloading and looking forward to that INS training mission! Muchas gracias y saludos! Iván

Hi Rudel, I just came across this set of mission, but I don't find the Cold Start for the F1EE, is it missing for the download or is it me who is mission something? And thank you for this amazing work!

world.searchObjects function not returning Statics Objects for Syria. When I try this script: in Syria, it returns 0 objects, however, if I run it in Caucasus, South Atlantic or Normandy 2, it returns the expected number of objects. Test missions attached. WS_test_SA.miz WS_test_Syria.miz WS_test_Caucasus.miz WS_test_N2.miz

Disclaimer: I have not tested or seen your code. I've seen this debrief slowness in some of my missions. In my case, it was associated with garbage collection: too many objects in memory at the end. I was able to improved it by making sure that any unused object was "nil'ed" out as soon as possible in my code. YMMV of course. Good luck!

Probably from an A-10A ... The Viper and the A-10C use the same grip

Here you go. Today I was able to reproduce the issue with both variants F1CE Uncommanded Ejection.trk F1EE Uncommanded Ejection.trk

@Flappie Just tested again... Tried to reproduce it in the CE for about 5mins (my neck got a work out!) and was unable... But it took me perhaps 5 seconds to get ejected from the EE...This was with the Quest 2 and the lasted Open Beta available today. Both test were done in flight.

I haven't flown much the F1 since my last attempt. Certainly not since the last patch. I have not touched any settings on the Oculus side in a while, and, to be honest, none of those setting seems to be related to this issue... Interestingly enough, I think that @JoeBoter report is the first non-Oculus one... I'll try to reproduce it again later today or tomorrow and report back... Will try both, the CE and EE, just in case (I think my last test was with the EE). JoeBoter, what version of the Mirage were you flying?