overalien

... so can we infer that this is a DCS and/or HeatBlur Tomcat Bug - alignment on Carrier does not work if the carrier is turning during INS alignment / start up? or is this a "feature" and works as designed?

that one is for OpenBeta 2.5.6 - my changes are documented in the code's comments. If you want the one that works for Stable or Openbeta 2.5.5, let me know. I will upload. They are not cross-compatible - ED changed the code with 2.5.6.

I used both an IBeam Shaker and the JetSeat together before. I found that the JetSeat performs significantly weaker when used like this compared to being used without "Combined Output" (weaker vibration effects). Because of this, I eventually removed the JetSeat and run on iBeam with Sound Module alone. Not sure if this is a software issue or is just subjective observation from my side. Regardless, I found little benefit of having both. The iBeam requires a lot of sound file tweaking (pitch changes) to come to its own, but once that is done, it is amazingly crisp, albeit "only" a MONO Shaker. I would like the developers of both to comment on these observed effects (weaker JetSeat effects when using combined signals) if possible please.

I checked this several times and can confirm that VAICOM replaces the stock GameMessages.lua with exactly the same file. I circumvented this by making a OVGME MOD with a modified lua file which displaces the game messages 300 pixels lower. Note: I made this file 'read only' in the file attributes - this prevents VAICOM from overwriting the file when it starts. This works perfectly for me since radio menus are never obscured by game messages and the scrolling in the game messages works perfectly. Interesting would be to ask @Hollywood_315 why VAICOM must replace the stock lua file with an unchanged one, as it makes no difference. Rather it should replace the lua with a file similar to my mod (modded file for DCS Openbeta 2.5.6 attached). Note: I made 2 modded files - one for 2.5.6 and another for 2.5.5 versions as these are different in the source code. gameMessages.lua

most of my issues came from a single ST waypoint off the map given to jester to enter after alignment and before taxi.

Same issue. Hsi points off by 15 to 20 degrees to target but the lantern and TID remain spot on. Sent from my iPhone using Tapatalk

DCS World TARGET profile for TM Cougar and Warthog + MFDs To answer your question properly. Axes only get stuck on gear transition. Sometimes the comms routine tends to lock itself into a toggle on commstate. Pressing comms briefly cancels it out again. That and the lights as described are the issues I had. Hope that clears it up [emoji6] Sent from my iPhone using Tapatalk

Update: setting LEDs to -1 solved it. Still suspect there is an addressing conflict with LEDs in that particular profile because it initialises with a comm state active LED and the lights don't flash on gear transition, but on the A-10 they work fine. For now no pressure since I solved the game breaker with your recommendation. flying with my son in MP can resume again. Thanks for that!! Sent from my iPhone using Tapatalk

....just to add a last little bit of info which might help: I also run the script on a Warthog HOTAS with 3 MFDs on a second machine and here the script performs flawlessly with the F-18 profile. It leads me to believe that the issue might be lurking in the Commstate Branch (where there are two scripts - one for Cougar and one for Warthog). It is only on the Cougar where i see the strange Commstate Init behaviour as well as the freezing axes - this specific to the F-18 profile only with all other tested aircraft profiles running fine with gear state transitions.

mine also died on me and i fixed it by gently pinching the USB plug 'a little flatter' (thumb and finger pressure only - no tools!) to provide a tighter fit when it gets plugged in. so my issue was a connection problem due to wear or corrosion at the USB connector. might work for you.

DCS World TARGET profile for TM Cougar and Warthog + MFDs Thanks. I tried the 0 setting on LEDs already to no avail. Reboots and vanilla reinstall of the scripts as well as Windows restore to an older backup also did not help. Will try with -1 on LEDS when I get back to the machine. Will report back... Edit: for the A-10 and other profiles with LED flashing active, the transitions are rock solid on my system. I therefore suspect something else than Target Stability.... Sent from my iPhone using Tapatalk

Hi Home Fries, With the latest script I have an issue with the Cougar and 3 MFDs with the F18 which I cannot figure out: in Gear Down or Gear Up transitions the joystick X and Y axes freeze up for 4-5 seconds before becoming responsive again. I noticed that there is no MFD2 LED flashing on transition as for other profiles. Instead LED 1 lights up steady and then goes out again. During this time controls are frozen. The script seems to report back some part of an Init routine regarding the airbrake config every time this happens. On other profiles the gear transitions work smoothly with LED flashing and no controls freezing. Another hint might be that when initializing the F18 profile, LED 2 on MFD 2 is lit up steady as if Comm state is active. This is also strange and may be an indicator that the script is stuck in an incomplete initialisation loop? I tried resets, reinstalls etc but made no progress. Would like to try an older version of the script to check some more things but not sure where to get it. Can you point me in the right direction please? Sent from my iPhone using Tapatalk

With me if was triggered by commanding Jester to Scan Level or Scan center while he was in TWS Auto mode. Sent from my iPhone using Tapatalk

Happened to me as well. He kept mashing the Manual TWS switch. Even switching seats and trying to break the loop was. Also INS is a mess for me. Not sure what he is doing back there.... Sent from my iPhone using Tapatalk

same for me: Baltic Dragon Enemy Within 3.0 last mission as soon as the camp capture starts - ground units and infantry moving here as well. Drop from 60 FPS to 16 -19 FPS.

...with the terrible FPS of 2.5.6. at the moment i cannot wait for the revival of this awesome tool. How are things progressing Sarge? no pressure, but some of us are rather eager...:D

I have replay issues with the A-10c as well..... Sent from my iPhone using Tapatalk

Yes it was significantly better before and is hard to use effectively in its current state. I think some tweaking is needed by ED in this one please. Sent from my iPhone using Tapatalk

OK read the thread about altitude before Delta. In 2.5.5 this does not seem to matter. I flew the mission back to back in both versions with identical Path Hold Autopilot. In 2.5.5 the trigger works but in 2.5.6 it does not. What is the altitude ceiling for the trigger after WP1? Sent from my iPhone using Tapatalk

Ok. M13 is definitely bugged as well. The initial radio briefing does not trigger. Sent from my iPhone using Tapatalk

The flight briefing in M13 on the way to Delta did not trigger at all. Maybe I messed up the radio tuning at startup. Not sure. Will try it again today and report back. Sent from my iPhone using Tapatalk

it looks like "Raider" does not move to the Artillery location. Hence all other triggers are not activated. Mission 13 also seems to have a trigger bug right at the start. Missions work fine in 2.5.5....

Glad I could help mate [emoji6] Sent from my iPhone using Tapatalk

Hi You need to open up and edit the profile in voice attack. Once open, there are two commands with a c# script in each. For the first "Record Audio" just double click the command to edit it. In editing there are two places which refer to stop recording in the script. Just choose the command and select edit. Edit those settings to add a button press setting from your hotas, replacing mine. It's all pretty intuitive. Just make sure when you edit that all the right boxes are ticked and you choose the right controller from the drop down.... and you use a free hotas key for it. You can do the same in the Play Audio command to stop audio playback if you want or just leave it if it's not important for you. This is what I changed in the default profile. It was set to use the Enter key to stop recording... Hope it's clear enough. Sent from my iPhone using Tapatalk

Here it is. All credit to the original developer, I just made a few tweaks to suit my needs. Note that DX21 on my HOTAS Controls "End Recording" as well as "End Playback" - I cannot use the kbd "ENTER" key in the default profile because it is used by DCS and would cause craziness there... To use, I add this profile as an"Include Commands from Other Profiles" to the Main Voice Attack Profile. To get this into Voice Attack and integrated with VAICOM you must Deactivate Plugin Support in Voice Attack (under Settings, First Tab) Set Voice Attack to start with VAICOM Pro Profile as default (under Settings, First Tab) Import the vax file in the attached zip as an imported profile Edit the VAICOM Profile's Options to include commands from this new imported profile Re-Activate Plugin Support in Voice Attack (under Settings, First Tab) Restart Voice Attack Edit the Voice Recorder Profile to modify the STOP commands "Recording" and "Playback" to fit your HOTAS (best to use an unused DX or at worst a single keyboard key if you have a free one that is not used in DCS) Audio Recorder & Playback Franz MOD.zip