overalien

Hi. I have an iBeam shaker and had the same issue. I had to use Audacity to modify the pitch of all sound files before I could get acceptable effects. The dynamic character of you shaker and amp make a huge difference and each setup will be different. For me a 20% increase in pitch did it. Lots of work but well worth it. Sent from my iPhone using Tapatalk

Hi all, I believe the effect shown here in the pictures is a result of mixing old export script mods with the latest update. I had this issue in the AMPCD and discovered that the export of all three MFDS now works without nodding any scripts. If you still use you old modified script files in this update like we did in the past to get exports working, this seems to be causing some weird stuff like this (like a kind of double export perhaps). When I removed my mods, all three exported screens in the f18 worked without distortions like this. Remove your mods and voila! The major issue with exported MFDS is however that the alpha channel is different for in-cockpit vs. Exported viewport. The exported alpha is a lot lower than the cockpit display. This is especially bad in the Tomcat for the VDI in red night mode, but is still present in day mode under certain conditions as well. Please ED can you look at this as the real issue? Sent from my iPhone using Tapatalk

Can confirm it seems to be not fixed yet. Sent from my iPhone using Tapatalk

Same problem here. Glide slope bar not moving at all and ACLS is dead. Sent from my iPhone using Tapatalk

I loved this campaign! Thanks for alleviating my onsetting boredom with SP missions and non rewarding, laggy online play with the Tomcat. This campaign has some really charming moments and is top notch for storyline richness. Well done! If this is your first, you have a bright future ahead of you, man. Voiced dialogues would be brilliant as an improvement as well as a few more missions with some more of that unpredictable and original action. I'm sad it's over after completing mine in 3 days flat. Looking forward to Version 2 or a new one entirely from you!

same goes for Helios guys. been like this for as long as i can remember.

Agreed. Jester seems to default to FM. I always explicitly ask for a change to AM because this bugged me for a long time. Sent from my iPhone using Tapatalk

Hi IronMike, Can you please clarify whether the issue of significantly different brightness of in-cockpit displays vs their exported counterparts is a module specific issue or a DCS core issue? This is a long standing complaint with not much (if any) feedback from any devs. Is this on a bug list somewhere? With the lighting adjustments this became more severe in the recent past. In the Tomcat this is particularly annoying for the VDI at night - turning down the brightness in-cockpit to an acceptable non-blinding level renders the exported image almost unreadable (too dark). A 1:1 brightness level between the two is all I ask for [emoji6] Sent from my iPhone using Tapatalk

nope, same beta version. looks like the settings import from a previous beta version corrupts the settings DB due to the added extra cat launch and wire trap effects om F-14/F-18. I reset and manually re-entered my settings. now i have the cat launch and wiretrap settings displayed properly and can edit them.

I can't get the HUD target designator to lock on a ground object in Computer Target mode Set-up and sequence is (applies with or without Lantirn POD in loadout): -Select Air to Ground Mode- -Master Arm on -Select GBU -Rel. Mode Single or Pairs -Ripple Time Step -Fuse Nose/Tail -Mode Computer Target -Slew up or down with VSL High/Low -Press PAL to designate point on ground Behaviour: HUD Designator moves slightly to the right and stays on Bomb Fall Line. Velocity vector and bomb fall line stay merged. designator does not lock on the ground. repeat PAL press various times (try long press, short press) - nothing. What am I doing wrong, or ist this a bug?

Tested. Had some trouble with SSA holding imported settings. had to re-import several times before they stuck. Symptoms were: start SSA manually - settings are in. start via DCS app - settings revert to default. re-import - they don't stick when SSA is restarted via DCS. rinse and repeat. eventually they stuck, so all ok there. strange. No cat launch effects at all when using only sound module - is it currently only functional with the JetSeat? also could not find a strength setting for this effect. is that also not implemented (yet)?

I have the same issue. Tried various resets without success. Sent from my iPhone using Tapatalk

Same behaviour here Sent from my iPhone using Tapatalk

I can confirm. Have same problem with instrument and console lights. The other light wheels seem to work fine. Sent from my iPhone using Tapatalk

Approach Indexer Lights Fix forgotten - Hotfix please? Deleted

I was referring to laser arm. Not the NWS switch. Sent from my iPhone using Tapatalk

I have had autolase fail often when using keybinds or DX buttons to arm the laser instead of the mouse click in the cockpit. Almost sure this is a latent and very old bug. Autolase is 100% reliable when using the mouse click in the cockpit to arm the laser, provided all other parameters are met of course. Sent from my iPhone using Tapatalk

In the latest patch all indicator lights received a temporary fix to compensate for lighting issues. great work and thanks for that HB!!! Unfortunately the Approach Indexer seems to have been forgotten and is still too dim to see in daytime. Kind of important for traps and landings... :) Can we have a hotfix please or is it "two weeks" again? :music_whistling::smartass:

This is a general issue with all modules where the exported displays have a significantly lower gamma than the in -cockpit displays. Let's hope that it is on EDs radar to fix as part of the general lighting overhaul. Please post liberally if you agree and support this as a much needed fix. Sent from my iPhone using Tapatalk

It's a long standing issue that has been raised by a few people repeatedly over time. It seems the fix is not a high priority for ED. Perhaps now that ED is focusing on lighting topics it may be a good time to post here. If enough people show interest, ED may consider raising the priority.... Sent from my iPhone using Tapatalk

You can also start typing your new alias by placing the cursor at the beginning of 'alias1' without selecting the whole of 'alias1'. When done typing, tap delete until 'alias1' is deleted. Then hit apply. This avoids the Notepad++ dance. As long as you don't overwrite a fully selected 'alias1', you can avoid the issue as well. Sent from my iPhone using Tapatalk

totally with you on this. let us hope ED finds time to consider it. UltraMFCD definitely proved how performance efficient and "simple" (from a UI point of view) this approach can be. kudos to Sgt. Baker for having braved the mountain of hacking effort to get the earlier versions to work and stay working. would a poll of user demand help to get ED's attention I wonder? I'll be a happy supporter being the owner of an Ueber-Export rig... ;)

This sounds a lot like what UltraMFCD was doing.... Sgt Baker is the expert who created this gem of an app. Currently I believe he is working on reviving it to work with the latest dcs release.... Sent from my iPhone using Tapatalk

Great insight thanks. I never thought of this very obvious fact!! So many bugs in OB can cause paranoia [emoji12]. Sorry for the confusion with TTI. I had similar behaviour in both your mission as well as TTI. I shall do a few tests, but I expect that you are 100% correct. Sent from my iPhone using Tapatalk

I get similar behaviour even after repeatedly following the usual fix steps for this. it is not really random, but appears to be triggered by non-ATC comms events or some Supercarrier ATC Comms - either directly after my own comm event or even just after a BRA Call from the AWACS or a wingman spotting a contact. Especially in this mission https://www.digitalcombatsimulator.com/en/files/3300558/ which has a lot of scripting, i get the menus popping up a lot. Something odd is going on with the scripts in the mission and VAICOM, I suspect. Suppression Auto Responses for own ATC Messages for the Supercarrier is also hit and miss in this mission.