Freefall231

Is this pretty major flaw going to be acknowledged at all, or is the MB339 just uninstall-ware now?

Thirded. Same issue. Noticed while validating some approach charts ingame and found the MB339 to be way off where it should be (mission set to same year as charts obv). Issue confirmed by flying same approach in a C101 where issue not present. Hope this gets fixed. Navigation a pretty big deal lol. Amusingly, put a portable TACAN next to a VOR, and program them both in the MB339 cockpit and switch VOR / TACAN nav and notice there's a significant difference between its position finding.

No worries. Was just unsure given your CBT tag. Yep. What's missing in the MODULE is: Click IFF on the UFC. Press IFF button/page on the MPCDs. Neither of these do anything ingame. What should then happen is something like: ODU populates with Mode 1 / Mode 2 / Mode 3 / Mode 4 Select ODU option. UFC scratchpad activates. Press UFC keys to enter value. Press UFC Enter to submit entered value. Press UFC On/Off to activate. Then its like you said, no further interaction/functionality with the official game - but it is another step towards a full-fidelity simulated cockpit. Outside the official game, SRS and LotATC mods/apps can grab those set values. This would be a secondary improvement/benefit as right now those that use it are alt-tabbing in/out to set this stuff. Cheers

Dont take this the wrong way @QuiGon; do you officially represent RAZBAM? (i dont know). Your posts read like they should be taken as such. The OP specifically asked the very pertinent question on when the Up Front Controller IFF functionality will be added. It doesn't matter what the backend or external mods do with what's set in the cockpit. As with practically all other modules - the cockpit system/interaction should exist. You're misrepresenting the raised question by stating things like 'there is nothing to do here for Razbam' and 'there is nothing missing there atm' - as that is absolutely not the case. The UFC IFF cockpit interface functionality is absolutely missing and needs to be added.

so by your logic; if transponders don't function in DCS and SRS is not part of DCS - then how do you explain why this in-cockpit functionality exists on practically every other module?

Frequencies added in the ME interface change for some reason when the Simulation is launched.

Plenty of modules have implemented selectable Mode 3 transponder codes functionality - regardless of if it interacting with the core or not. Plenty of modules interface with SRS. Even Razbams own Mirage 2k does, and i bet the F15E will. Seriously...

Hi, just downloaded this. Looking at the standalone functionality as we do all our flight planning in CombatFlite. When I open the .exe i can only select 'Caucasus' under terrain. Will this prevent us generating .dtc for other maps (we dont fly on CCS at all)? Thanks

hotfix is expected when? Hope 'next update' isn't implying next month? that would be very bad. Beta or no beta, issue of this severity should never have made it to the customers. Sorry. P.S my personal best FPM at the moment is 563 lbs/min.

incorrect. occurred multiple times to multiple users in our community.

EHSD > MAPM > TRUE is boxed by default again. It was unboxed by default in the previous version, following many bug reports. It was a resolved bug that has reappeared.

When ext fuel tanks loaded on indoard pylons, you're unable to select any ordance loaded on outer pylons. Options do not exist on stores page in any master mode. Issue sometimes clears if you rearm a second time. Edit 26 Apr: Added info: Occurred multiple times/different sessions on multiplayer session. Occurred once with multiple users rearming at same time. Have been unable to reproduce in singleplayer, or in multiplayer on my own.

Hello, Just updated to todays patch (steam user) 2.5.6.59398. Unable to log in on main menu with correct credentials - keeps saying 'incorrect login or password'. Multiplayer completely greyed out and unavailable. Have done system restart, steam restart, game restart. issue persists.

Hello, User error on my part, apologies. Im seeing the SITE work correctly relative to correct delivery table Sight Angle mils. Thank you for responding.

Hello, Believe there is an issue with aiming carets: Process: - Stores page - Select Bomb/Gun/Rkt - Box SITE - ODU select SITE - Enter calculated Sight Angle Mils for desired Target Placement Angle, per Z-chart (i.e. set 30, or 22 as shown). - Current result/behaviour is aiming carets incorrectly placed ABOVE the velocity vector. Problem: Aiming Carets should be below the velocity vector. Their function is to aid Target Placement Angle management during Dive deliveries. You don’t want your TPA above your VV because then you’re flying shallow of your planned dive angle. Edit: Not sure about rules for quoting references here, but can quote multiple sources via PM if needed. Annotated screenshot attached. Problem marked with exclamation mark. Thank you to consider.