Draken35

I did it by loading MIST and the Range script in (different) MISSION START triggers coordinated by a flag. Look at the triggers in the mission I attached above.

Gotcha... Hard to say without opening your mission.. Anyway, take a look at mine, I eliminated the need to join as an observer first I don't see how adding an aircraft would break the script. If it an old mission then it is probably using an old version of the script, which broke with a DCS patch earlier this year. Ciribob fixed it on February. Look at the first post in this page Good luck!

Nope, I don't have any WWII stuff yet...Waiting for the Mosquito and/or F4U. By your description, what I think is happening is that you are getting into the cockpit before the range script is loaded. When that happens, you don't get the F10 menu for it or strafing reports although it will report weapons drop. Attached, is a mission with no mods or aircraft (add your own) in the Caucasus map, Mist 4.4.90 and the latest range script. In this mission, you can jump directly into any client a/c . I suppose it should run in MP but I have not tested it outside of SP. I'm running OB 2.7.4.9xxx CA Range - No mods.miz

Huh? I used it every single day in SP with no issues. (Mist 4.4.90 and the latest version of the script)

Ah! for a second I tough that somebody was working in populating that area of the PG map…

Huh? I might have missed that memo... Details please

@jacobs can you describe your issue and tell if you are a VR or pancake user? The font itself is readable and the Gain issue is mostly gone. There is still the need to play with the gain, contrast and sym rockers depending on lighting conditions but I would think that is realistic ... My issue currently is a vibration effect that occurs only in the MPCDs of the Harrier. When I use VR zoom or get close to the screen, the vibration is gone and the MPCD looks great, provided that I adjust gain, contras and symbology. I've been testing different AA settings at DCS and NVIDA level and they don't have an impact on the vibration even thought I can see the effects of the AA setting in other parts of the Harrier cockpit/world and in other modules. I'm a VR user / Quest 2 Edit: Ah! Failed to read that.... Most likely is something in you settings... I fly the Hornet too (and the Warthog) and I have no issues with those...

Seconded.

Anytime and welcome to the Harrier!

Fix is WIP Check this thread:

I haven't seen it since I turned off the parser (my post of May 12th above)

Thanks much for the Solomonic decision ! On a quick glance, the Manual is looking top notch. I certainly will check it out in detail. The Combat Flight tidbit is quite interesting. I'm interested in that software too, just waiting for it to be updated with the latest Map changes to take the plunge. Edit to add: A small suggestion, if it is not already considered. In the weapons section of the manual, you could add a line per weapon specifying the time frame on which said weapon is a valid loadout.

Well, took a quick familiarization flight with it... It is obvious that is very early in the development but it looks promising ! Flew it in VR and I'm keeping an eye on this one

https://github.com/PucaraPastrana/PucaraDCS/releases/tag/V-0.0.3b Just took a quick glance at the PDF, seems to be a clickable cockpit??? I downloaded but cannot test it till tonight unfortunately.

@horstweihrauch Kappa is right, you have to drag the root folder of the pack into the mod tech folder of your saved games: And yes, this mod is required. It provides a FCLP (Field Carrier Landing Practice) surface that mimics the Tarawa and I use it in the FARP for VL practice.

Place an invisible FARP and the Harrier in it

Had something very similar yesterday after a motherboard bios update... After some hair pulling, I was out of ideas and opened the Oculus software and clicked on devices....To my surprise, I saw a recommendation to connect my link cable to an USB 3.0 port (which is were it is connected to!). So, I ran the port/cable test and it all went to normal. Just an idea of something to check if you haven't already. Good luck!

this: works very well.

Not sure if it is working properly in 2.7 ... I remember testing it in 2.5.6 and it did work, if your were able to find flat terrain long enough. Of course, the AI cannot use it.

Excellent Luiz! Glad to hear... In this time and age, with the pandemic, is hard to tell ! And yes, Due to work too, I cannot "fly" much during the week and get to the weekend experiencing withdrawal symptoms too

It was mentioned in their Discord that the TOO issue was fixed in their internal build and was waiting for ED to push it. That was before 6/23. Unfortunately ED did not pushed 3rd party fixes in the last patch

Thanks! Good to know that it is just normal life

It has been a couple of months without updates on Github or the team posting here.... Hope everything is ok with them....

or just create the TP's in the EHSD Data.... Either way we need to type coordinates... The beauty of using the TOO is, that the target can come directly from the sensors, which is, I assume, what OP intends ... For sure, is something I want

I was referring to the context of your initial post about " multiple JDAMs in one strike without switching to multiple TGT" ... In order to do this, you need to select the TP you want to attack in the JDAM configuration by "colonizing" the corresponding TP's as you know... Well, the bug is that we cannot "colonize" the TP if it was created from a TOO. We need to wait until ED push out the next 3rd party update to get the fix.