TAIPAN_

Works fine with BS2 uninstalled (so far)

You can swap the module in campaigns by editing the XML files in each mission using a find and replace. The .miz files are just zip files, associate them with winzip and they will open. It's a bit tedious opening them one by one but I managed it with some older A-10 missions.

The BS3 default helmet sight position is way too high to be comfortable especially if zooming in (appears near top of HUD). There is a setting in special options, but it doesn't not change the displacement of the ring (unlike BS2). Attached are two screenshots, one with minus 15 displacement, one with plus 15 displacement both are at the same location on the screen. nullAlso attached are the tracks for both settings shark bug1 - minus 15 displacement.trk shark bug2 - plus 15 displacement.trk

2.8.1.34437 Open Beta AH-64 line states fixed: "Fixed: Exported TEDAC creates a double image on the TEDAC in the cockpit." However when I test this in instant action mission the double image is still there: These are the two lines commonly added to TEDAC_init.lua in order to export the TEDAC: "dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("AH64_TEDAC")" Did the fix not make it into the patch, or do I need to change what's added to TEDAC_init.lua to export it without the double image?

If it's not managed by DCS what is it managed by? There are other similar solenoid electrically held switches in DCS that do have discrete bindings available. I don't see how being electrically held would mean you can't bind a button to turn it on or off?

Looking to install the Viggen mod soon when I get back from travel. Wondering if any issues with todays Viggen update?

Thanks for that. For the liberation mission, it will be in this track attached. I noticed that it gained the similar extra folders like the "Avionics\A-10C_2" folder in the track, however that folder isn't there in the track from my previous spawned flight on the same mission. Something happens during the respawn process after dying. Possibly if you respawn it may do a prepare mission to get your plane recovered back into that slot. I worked around it by choosing a different slot, or going back to spectators and then going fresh into the slot. There's a similar bug in the Hornet on the supercarrier when you respawn into the same slot it puts you on the Cat with wheel chocks, then dumps you into the water when you try and launch. The workaround is the same there. retribution_nextturn-20221215-135449.trk

These are good questions. I don't have the source data to say what the correct HOTAS was on those particular aircraft. The reason I raised it was because ED had changed the A-10C v1 HOTAS during the release of v2, there were many changes. I was wondering if these 4 items were simply missed in that change process. And of course the other reason is personal convenience In any case I'm curious to know if it is historically correct as is. If it is already matching 2008 aircraft then my wishlist item might be something for the "special options" settings page with a tickbox for "use common HOTAS layout with A10C II". If there is no data to tell either way, then it's still a Christmas wish as well. Happy to hear any comments from Pilots/SMEs who can remember.

Thanks, it's a mission I've used many times for training that is entirely possible I accidentally hit it being the menu item right below the fly item. However it also happened in a multiplayer mission that was generated by DCS Liberation and put on a server. The first flight the DSMS was ok, but after dying and respawn the DSMS had the same issue as the prepare mission. Would that be a separate issue or can you add that to the existing issue to fix the respawn error as well?

Steps to reproduce in multiplayer: -Spawn in one aircraft, load weapons, load MFCD pages and DSMS loads correct -Die -Spawn again in same slot without switching slots, DSMS will have red items with the previous loadout -Load all doesn't succeed in replacing the weapons in the DSMS Steps to reproduce in singleplayer: -Execute a mission in the mission editor including air start -Close the mission and change the loadout -Next mission the DSMS page can be stuck in the same way. Track attached from mission editor test. DSMS stuck on previous mission.trk

After the v1 HOTAS was updated to more or less match the v2 (excluding the Scorpion HMCS commands), there was 4 functions leftover that didn't get updated: The A-10C v1 is still flown alot for the older campaigns, as well as the cold war servers and multiplayer set in older timeframes. It's very confusing to learn the HOTAS and have to swap out commands each time we switch between v1 and v2. It would seem the entire HOTAS can be copied, just excluding the HMCS commands. Can these 4 commands be ported back to the A-10C v1?

Page 91 in the manual shows the HOTAS commands as per this screenshot. The circles commands DMS FWD Long, DMS AFT Long, and DMS Left Short have no function in the sim. Please fix the defect or document the pre-requisites to make these functions work. Alternatively if these functions are never intended to implement, please remove from manual. null

The Anti-skid switch only has a toggle keybind, and doesn't have a way to map it to a 2-way switch i.e. an ON and an OFF binding. If I add the bind myself based on the clickabledata.lua information, it does move the switch however it doesn't change the anti-skid status and the warning light remains on. I believe this needs a new function added by the team to bind to.

Added to wishlist:

Please implement this very useful function, described here:

What does your export.lua look like? Does it change when you run the Winwing software? Sometimes you can solve these problems by changing the order of entries in the export.lua.

Thanks, you mean it comes on the same release as Black Shark 3???

Thanks, this works to fix Devrim's english custom cockpit that I'm using (fixed all the warning lights). However it doesn't seem to fix the back wall which is still in Russian. How does this section of the cockpit appear to you? null

For #3 - these are the 10 waypoints, in the same location: null

Found 4 problems when assigning multiple waypoints to target points: 1. When switching back to waypoints from target points, the waypoints can only scroll down and not up. Eg from target point mode switch to WP mode and select waypoint #4 (or any number). Pushing Up will jump to waypoint 1 and you cannot move up to further waypoints unless you use the ODU to select them manually. Pushing Down will move to Target points like it doesn't want to move out of TP mode. See Tracks 1a and 1b attached 2. Target points can't scroll down, scrolling down switches to Waypoint mode. See track #2. May be same type of bug as #1 in different mode 3. When assigning a target point, if the ODU menu for TOO is already open before you push DESG it will assign an erroneous target point (somewhere > 300 miles away) instead of using either the previous designated point or the new point you are about to designate. Even if pushing DESG then assigning it will use the erroneous location whenever the ODU TOO menu is opened before pushing DESG. See Track #3 4. In two instances of testing the above, the waypoints were overwritten with the erroneous location mentioned in point #3. Unfortunately I didn't have a track of this, and trying to reproduce it I'm unable. It involves certain combinations of waypoint select->designate->TOO, and GBU stores assignment. If it happens again I'll save a track but please take note if the waypoint seems to move. 1a. AV8B Waypoints Get Stuck on first.trk 1b. AV8B Waypoints Get Stuck on first.trk 2. AV8B Can't scroll down on Target points. Scrolling down switches to WP mode.trk 3. AV8B Target point takes eroneous coordinates if push DESG while ODU menu open.trk

Just mapping keys and starting to learn this beast. In the Huey, Hip, and Blackshark there is a Cargo Indicator that looks like this screenshot. However in the Hind I can't find it. Curious what the reason is? Is it something to come later because of early access? Or is it just not being done anymore because not realistic or something? Or is it actually there I just haven't got it to work yet?null

Walleye cannot uncage from the center MPCD, the uncage button does nothing even when a target is designated. Correct setup is confirmed by moving it to the right DDI with the same target and same Stores setup it will uncage instantly when the Cage/Uncage is pressed. Track is attached showing Designation, then setup on Center MPCD. Cage/Uncage is pressed many times when the MPCD is SOI but it fails to uncage. Swap to Right DDI and cage/uncage works. This has been tested in single player and multiplayer, with and without datalink. The only common issue is the Center AMPCD being used. UPDATE: -A few more tests showed I could uncage the center AMPCD if the designation came from the SEA radar and not from the TPOD -Also had some failures uncaging from the right DDI if designation comes from the TPOD, but the SEA radar and waypoint designation worked to allow uncage. So it's not 100% clear of the cause but it's related to the flow using the TPOD and possibly the center AMPCD. Walleye Uncage fails on TPOD designation.trk Walleye Uncage fails on center AMPCD.trk

Go to your windows profile folder called "Saved Games", then DCS subfolder, then to config folder. Open options.lua and you can see "multiMonitorSetup" will point to the file you selected. Back up options.lua the rename it. Open DCS and it will create a new options.lua with default settings. You can copy the multiMonitorSetup from the default into your backup if you would like to restore the other settings. Go to your windows profile folder called "Saved Games", then DCS subfolder, then to config folder. Open options.lua and you can see "multiMonitorSetup" will point to the file you selected. Back up options.lua the rename it. Open DCS and it will create a new options.lua with default settings. You can copy the multiMonitorSetup from the default into your backup if you would like to restore the other settings. Go to your windows profile folder called "Saved Games", then DCS subfolder, then to config folder. Open options.lua and you can see "multiMonitorSetup" will point to the file you selected. Back up options.lua the rename it. Open DCS and it will create a new options.lua with default settings. You can copy the multiMonitorSetup from the default into your backup if you would like to restore the other settings. Go to your windows profile folder called "Saved Games", then DCS subfolder, then to config folder. Open options.lua and you can see "multiMonitorSetup" will point to the file you selected. Back up options.lua the rename it. Open DCS and it will create a new options.lua with default settings. You can copy the multiMonitorSetup from the default into your backup if you would like to restore the other settings. Go to your windows profile folder called "Saved Games", then DCS subfolder, then to config folder. Open options.lua and you can see "multiMonitorSetup" will point to the file you selected. Back up options.lua the rename it. Open DCS and it will create a new options.lua with default settings. You can copy the multiMonitorSetup from the default into your backup if you would like to restore the other settings. Go to your windows profile folder called "Saved Games", then DCS subfolder, then to config folder. Open options.lua and you can see "multiMonitorSetup" will point to the file you selected. Back up options.lua the rename it. Open DCS and it will create a new options.lua with default settings. You can copy the multiMonitorSetup from the default into your backup if you would like to restore the other settings. Go to your windows profile folder called "Saved Games", then DCS subfolder, then to config folder. Open options.lua and you can see "multiMonitorSetup" will point to the file you selected. Back up options.lua the rename it. Open DCS and it will create a new options.lua with default settings. You can copy the multiMonitorSetup from the default into your backup if you would like to restore the other settings. Go to Windows profile "Saved Games", then DCS subfolder, then to config folder. Open options.lua and you can see "multiMonitorSetup" will point to the file you selected. Back up options.lua the rename it. Open DCS and it will create a new options.lua with default settings. You can copy the multiMonitorSetup from the default into your backup if you would like to restore the other settings. Lol sorry but mega forum glitch looks like it multi-posted

Hi, The SPO-15 is missing some information. It's possible it is missing medium range SAMs completely? Firstly - it is showing incorrect threat at bottom of the screen. In DCS there is a threat of Medium Range SAM primary (Box and letter lit), as well as secondary Short Range SAM and AWACs (secondary is just the letter lit but not the boxes above). On the Android App the Medium Range Radar is totally missing from being highlighted Secondly the dot at 90 degrees left is not lit. Thirdly I am being locked in DCS (red circle), but not locked on the DCS UFC Android app. Assuming all 3 missing items are related to the medium range SAM. Can you please try and find what's missing? To reproduce it, I can take the Su-25A and fly on Enigma's cold war server Syria map. Maybe 5 minutes flying from base toward enemy lines I'll be litup like the attached photo.

Note when testing/reproducing - I noticed a case where the bug does not occur. In a single player mission setting the countermeasures in the mission file, re-arming does NOT overwrite them and works fine. But in multiplayer when setting them on the kneeboard then re-arming DOES overwrite. So it needs to be tested by manually changing them as a multiplayer client as well, not just in a single player mission.