gulredrel

Still an issue in OB update DCS/2.8.3.37556 today. -4.5 / +7 g bump during taxiing back to parking space at Kobuleti. 20230310_MB339_test_g-spike_blackout_taxi.trk

Thanks, confirmed fixed in today's OB update DCS/2.8.3.37556.

Thanks @6S.Duke confirmed fixed in today's OB update version DCS/2.8.3.37556.

Fictional, but looking quite nice. Thanks to ZedTank for the livery: https://www.digitalcombatsimulator.com/en/files/3326667/

It depends on ED releasing the patch, you can follow this thread to receive announcements:

Ah, okay, thanks, I see now. So this looks similar to my findings being dependent on roll angle and target offset angle.

Have you selected AA guns or missiles? I think the symbology together with the intercept cue is only visible with weapon selected. Could you please retry if this changes something? I've posted some pictures in the second thread. Looks a bit strange even with the symbology but I don't use TIR or VR, only shifting view with cockpit camera position. Would like to see the results in your video. @fausete Maybe these threads could be merged?

Not quite sure if this is it. I moved my head with cockpit camera move forward / left / right / back in the following position, max forward: one second later and some degrees nose up, the square comes into view: here it is visible on the left side, okay. But here to screenshots with two seconds apart and markings on this time: no more visible two seconds later without changing head position, only steering a tiny bit nose lower: Also looks like rolling the aircraft, the dot gets lost at the edges? View forward and in so that there is so much of the glass visible with the pitch ladder, the dot should be there as it is visible in image three well away from the pitch ladder if you would draw a rectangle around pitch ladder?

Not using VR, will try to shift my view to see if the square gets visible before the target is behind the glas.

*bump* I'm on stable, just ran into it cause I forgot to set radar to emit from standby position after takeoff and wondered why there is no radar intercept symbology with target locked. Used the F1 CE of course in stable. @fausete Is this known issue?

@Vibora: Is still an open topic as commented in the post below!? Also do you have the radar command reticle not working every time!? Or is it weapon dependent? Need to investigate and maybe report in a different post.

Thought the same trying to find the locked target without knowing it's altitude in the clouds.

Question to all having the com menu not opening. Could you please check if you had TACAN selected as NAV source when it is happening? Try no selected nav source or VOR or RNAV and see if this helps. Details here:

Still an issue. But I guess I narrowed it down. Communication is no more possible, as soon as TACAN station is tuned and TACAN is selected as navigation source on the NAV panel. Once you use no nav source or VOR or RNAV, you can talk to and receive ATC information. Track attached showing Com2 inbound and abort communication with Kobuleti ATC. After selecting TACAN as nav source, the com menu will not open. deselecting TACAN nav source, everything works again. PS: There's also something with the keybinds and COM1/2 selector. I've mapped com1 PTT and com2 PTT to two buttons, but only the com2 ptt button really works but the com menu only shows COM2 even when talking through com1 radio(?) It's also in the track but that's a bit confusing. 20230211_MB339_no_COM_when_TACAN_nav_selected.trk

New tracks in discord PM and also attached here. Still happening in 2.8.2. My workaround is zero winds, of course, this only works on own SP missions not MP when weather is forced to some other than zero winds at groundlevel. 20230208_02_MB339_multiple_g-spikes_blackouts_while_taxiing_and_damage.trk 20230208_MB339_multiple_g-spikes_blackouts_while_taxiing.trk

Part of the latest changelog is this: "Moving the throttle to idle before the RPM are above 300 may lead to fire or over-temperature due to accumulation of fuel faster than before (IMPORTANT)." Maybe wait a bit longer than 300 rpm on the gauge before going to idle? Looking at it parallax error could be, that you haven't yet reached 300 rpm? Also monitor EGT gauge.

For me it wasn't an Apache but an UH-60A AI dipping the nose and explodes. 20230203_UH-60_AI_RamatDavid_taxi_explosiont.trk

Maybe this is a related issue? I suspected lighting changes back then.

Looking forward to this as I'm constantly rotating through the modules I own coming back to the older ones too. Flew the Oilfield Campaign years ago. Back then without Syria map and new lighting, Huey and Mi-8 are a new experience with 2.8 and it's Core improvements. Created little transport SP mission on Cyprus with Huey or Mi-8 just to fly from location A to B, C and back to A with different sized cargos using different navigation equipment.

Development progress looks a bit frozen to me. I'm currently using the Mosquito in the trial version as I wanted to see, if I should buy it in the Bundle with the P-47. The sensitive tailwheel assembly bug got me in my first taxi attempts as I used the Mossie at Kobuleti the tail wheel left the taxiway and returned and broke even the taxi speed was quite low. This bug was reported in June last year... Graphics and cockpit are great but this progress... is the P-47 in a better state, haven't tried this one and don't know if I should money on that bundle or better wait?

Don't know about the key I use wheel brake axis on my pedals. Maybe have a look at your control bindings if there are any conflicting mappings.