TAIPAN_

When designating a target with the TGP, the first Laser Maverick will always uncage automatically simply by setting the maverick page to SOI (sensor select switch in the direction of the Maverick page). Once the first Maverick is fired and a new target is designated with the TGP, the behaviour changes and all future mavericks remain caged during the same procedure of TGP Designate -> Sensor select set Maverick page as SOI. Expected behaviour would be that the behaviour of the system would remain the same if performing all the steps from scratch, but it seems there is a state change once the first maverick is fired future mavericks always require a manual uncage. Track is attached, first Maverick uncages automatically. 2nd Maverick you can see it fails to uncage. (Ignore maverick hitting the ground and targeting the ground, the moving targets in the track are in a different position to where they actually were but the uncage behaviour is the same) Hornet 2nd MavE does not uncage.trk

Would love a Hornet version, there's so many setting/preferences we have to do to get the hornet in a fighting state every mission. The way the Radar is setup by default is not ideal, it would be great if we could pre-configure stuff like track timeout, radar bars, azimuth etc that is saved per each weapon select switch. The radar cross section and target size setting on the Sparrow/Amraam stores is not ideal, would prefer it default to small size. Default DDI pages based on A/A and A/G would be awesome, as the SA page is much better on the left DDI instead of the center. However I think this is a limitation in the real hornet as well I don't believe they can change it. Regarding multiple waypoint sequences, I think 99% of people only use SEQ1. The waypoint coordinates can now be done in MGRS as well, except for JDAMs/JSOWs which still can only be done in the old format when pre-planned mode.

Version: Current Open Beta 2.7.9.18080 Steps to reproduce: -Load 4 JDAMs in mission, with Hornet in air -Stores page, select QTY, select all 4 JDAMs (note its currently in PP mode by default) -Select TOO mode on one of the JDAMs while all 4 are selected -Try to change back to PP mode. -Press STEP, note that it will revert back to TOO mode every time. Even if you step through all the stations and select PP mode, it goes back to TOO mode. Basically if you have multiple JDAMs selected, once you select TOO mode there is no going back to PP mode. Also tested releasing the multiple JDAMs in this situation after changing back to PP mode - only the first bomb goes to the PP target, when they come off the rails bombs 2, 3 and 4 switch back to TOO mode. Expected behaviour is that switching to PP mode it should stay in PP mode. Track is attached. JDAM stuck on TOO mode.trk

Great thanks!

No worries thanks. The kneeboards are very good in this release I should be fine and had pretty much mastered the old version already.

What are the changes in v1.15? I saw there are some optional components, but if we don't want the optional items - should we just stay with the previous version? Or does the core mod have some texture improvements too? Thanks for the mod, it's keeping the F-5 alot more active for me

Hi @Rudel_chw I just realised I have your normal procedures summary PDF of the NATOPs procedures but no idea where or how I got it, and I seemingly have never used it yet Is that still valid for the full release of v2? I know it's based on NATOPs but has alot of references to the sim aircraft with screenshots etc.

Thanks for these!

If you guys are able to get SimShaker working with DCS UFC by changing the pw-dev-script ports - please report back. I'd love to get the SimShaker but don't want to risk any conflicts because this app is a big part of my setup.

Hi Guys, Since the recent integrity check changes in OpenBeta, do grayscale sensors still fail the integrity check?

Thanks, its been coming up in DCS Liberation and there's nothing they can do on their side if we use these planes/bases. Hoping it gets solved in future

I thought you could change the port?

This is actually very easy, as long as it's a valid indicator with the right lua file available. All you need to do is add 2 lines of code to the bottom of the lua file and it will create a named export. For example in the Ka-50 I export the EKRAN by editing this indicator file: D:\DCS World OpenBeta\Mods\aircraft\Ka-50\Cockpit\Scripts\EKRAN\Indicator\Ekran_init.lua Backup first then add these two lines to the bottom of the lua file: --Add 2 lines to the end of xxxx_init.lua in the indicator folder & set name I want (replace MY_EKRAN with whatever you want the viewport to be called: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("MY_EKRAN") Then just configure a viewport in your Monitor Config file to position that named viewport. I recommend putting your edited indicator file into JSGME mod manager, because updates can overwrite these files.

Just want to say thanks to @Munkwolf and @Quaggles, I had the old version and I've been sitting here coding Lua for the Ka-50 and A-10C to map to my new cockpit gear and it's taking hours.. Just discovered a new version with loads of new keybinds available is going to save me a huge amount of time! Thanks alot

I was going crazy wondering why my flashlight is stuck on white.. I can confirm the bug you've found is also present in the Open Beta version.

Tested with F-14B as well:

Version: DCS Open Beta 2.7.7.15038 You can see in the screenshot that only one AI aircraft on blue side was able to escape and takeoff. All red side was OK because no F-14s on that side. BLUE aircraft takeoffs - only one (because BLUE has F-14As): RED aircraft takeoffs - all (because RED has no F-14As): F-14As wings open before taxi: Mission & Track is attached, with AI flight plans etc. This could either be fixed by: a) Change AI behaviour to keep wings swept back during startup and taxi; or b) Change collision width of the tent hangars in Persian Gulf airbases (and any other places that they get stuck) AI Aircraft Stuck Track.trk Mission Log.log Mission.miz

Thank you sir!

Hi @pet333r Is it possible to add the warning panel for the Huey UH-1H? Its still very popular especially with multicrew now, and warning panel is the most useful to have. Thanks!

Screenshot attached at 200ft, 50m from the runway. Training mission is supposed to be a visual approach. Need to remove fog/clouds from these old training missions. Mission Name = "Landing Solo Practice"

Good idea for a server, I'll check it out thanks

I think most people got a second device for this, for example my main tablet is quite powerful I wouldn't want it mounted in my cockpit getting wasted. Got a cheap entry-level tablet to mount permanently and it works great. Second hand tablets would work too, I find it doesn't need much processing power.

Thanks, must be something to do with how UI layer changes get queued for saving. They must override all other control changes even if they don't exist in both. Only workaround is to exit and restart the game between switching controls to edit... but I suspect many don't know the cause and just get annoyed

To reproduce this bug: 1. Map controls on any plane (e.g. tested A-10C II tested mapping controls) 2. Switch to UI layer controls 3. Map a control (e.g. tested mapping BDA show/hide) 4. Check A-10C II controls to see that recent assignments have been removed I suspect when the UI layer gathers the data about all planes mappings, it might gather from the config file instead of whats in memory. When committing the UI layer change it commits the old controls (just a guess). I've noticed this bug was here for a while I lost controls, but only recently isolated the cause. This is extremely frustrating for someone who maps a whole HOTAS, w hole cockpit worth of gear across a whole plane it goes in both UI layer and in the plane.. then when the mapping is lost it takes a long time to redo it. Can it be fixed in future patch?

Awesome, thanks all