eifionglyn

Thankyou - I stand corrected. I'd have thought the ADIs displayed data from "some other" system, rather than being the data source. Clearly I am mistaken. That's what I love about DCS, always more to learn!

As title. I can't grab a track at the moment but this is easy to replicate. Recenter the right seaters ADI and the pitch / roll AP turns off. I can't imagine that this would be the intended behaviour.

Lighting for the doppler hover indicator or the doppler nav system doesn't turn on. Yes I've turned on the 5.5v doppler lighting switch, the two rheostats in the doorway and the one behind the pilot/navigator's head. Tracks for cold start and hot start attached. Apologies to whomever watches the cold start track as I fail to start the engine a few times. It was dark. mi8_doppler_light.trk mi8_hotstart_doppler_light.trk

Goddamit I thought I was going mad! Don't know if it's related but the cockpit lighting for the doppler systems no longer turn on either.

As the title really? What does it do? What is it meant to do? Far as I can tell, it doesn't really do anything for me. I see some of the youtubers say hold it as you pull collective for takeoff, but I really can't discern any effect if it's pressed or not. I read CDR stands for 'cantering device release' so I'm guessing in the real Chinook it temporarily turns off the mechanism providing stick forces on the cyclic, but does it have any relevance in the sim with a spring-cantered non-FFB joystick?

Refunded sadly. I love the F15 and will rebuy as and when ED and Razbam resolve their difference and state a public commitment to continued development and support.

I've had it happen a few more times since my original post. I think it's definitely a thing - but can't find a reliable set of conditions to reproduce it. I will try a bunch of air starts and post a track file if I see the behaviour. (have not tried air starts yet because I'm an odd one and enjoy manual cold starts!)

When it was first released, I was able to hit the target reliably with Mk82s in DT mode. However since the latest patch they are now dropping consistently short. I notice the bombing table calculator is now showing some different fields than it did before so something has changed.

Yep I had it again this morning, it's definitely a thing, but by no means every time. I notice he often gives a 'no can do' when commanded to acquire ground target ranging, and then goes on to get a ground lock anyway. It's feels as if one press of the button is sending multiple inputs to jester.

Tried to reproduce the behaviour and was again unable. Delivered Mk82s via DT, and subsequent air engagement the context button behaved as advertised. I think we can put this down as a transient error, or more likely operator error on my part.

Tested again this morning and was not able to reproduce. In both air start and cold start SP missions long press of the context button made jester attempt a lock. Not sure what caused the issue yesterday. Perhaps it was I had already used the context button to acquire ground range in a dive-toss bombing and it was somehow still trying to lock the ground. I will test again.

With a radar contact in focus under the radar cursor, a long press of the 'Jester Context Action' should command Jester to lock the target. It seems it doesn't interpret the long press correctly. Feedback from Jester is 'focussing on your guy' but no attempt to lock. If I command a lock from the wheel in the same situation, lock is achieved immediately, so I don't think the issue is the target is out of parameters to be locked. This happens with both a hotas button or a keyboard key assigned to Jester Context Action. I've tried clearing all bindings for Jester Context Action and re-assigning just one without positive effect. The long press of 'Jester UI Action' to close the wheel does work as advertised, so my system is correctly passing a 'long press' input to DCS. The issue appears to be limited to the 'Jester Context Action' control.

Worked out what my mistake was. I'd used the KC135 MPRS as my tanker, - stupidly assuming from its model that it has basket and boom available. It does not, in game it appears to be basket only. The boom is purely aesthetic. I've now added a regular KC135 and it does talk to me. The KC130 (basket only) does not, presumably because I'm not equipped to refuel from it. Bit confusing, I'm also not equipped to land on the carrier, but if I tune to their frequency and declare inbound they at least tell me to bugger off!

This is just a SP mission I've thrown together myself. Nothing fancy, just has some Bears circling at 10,000 and some trucks on the ground to shoot at, a tanker and a carrier. I use it mainly to learn an new module or when I need a refresh. Edit: The carrier will talk to me. It's just the tanker. I'll check its settings again.

Yep, I'm using MIC Switch FWD and MIC Switch AFT depending on if I want to use the primary or aux radio. Oddly enough I've noticed that Anderson ATC will talk to me on 250.1 once I start rolling down the runway. Still can't raise them on 126.2, and the tanker still ignores me.

Single player mission, nobody will talk to me in the F15E other than the ground crew. Tried with easy comms on and off, makes no difference. I use multiple other modules in the same mission, no comms issues with them. Anderson AFB on 126.2, Tanker on 251. Have read the manual and pretty sure I have the radios on, volume up, mic on etc, correct frequency tuned. Is there a secret mute all radios button I've inadvertently pressed, or is this a bug?

I've also tried it deliberately setting a wildly wrong QFE, it makes no difference. Obviously it moves the waypoint / target circle, but as I thought, that's just there as a guide to the pilot to visually acquire the target, it doesn't factor into the jets weapons employment parameters for rockets when using AGR.

211 turns on the fixed sight. 220/221 is target motion measurement on/off, which I believe is off by default. I have tried it with both and it doesn't seem to make much difference. Right here's a track file, air start 10km so away from the disused airfield at Kobuleti. There is a single truck in the middle of the runways. viggenRocket.trk

I have dialled in the correct QFE calculated from the F10 map, and verified this is correct by comparing the pressure and radar altimeter readings when flying straight and level over the target area (trucks on an airfield so it's flat). It's my understanding that QFE setting is irrelevant for rocket delivery in ANF master mode as we're using radar ranging. I'm placing the pipper on the target, unsafing the trigger, keeping the pipper stable on the target, waiting while the range bar shrinks down and flashes and only pressing weapon release when the 0.5 sec 'wings' cue appear either side of the pipper. I'm not sure how to edit a track (or record my screen for that matter) but I'll look into it as this is pretty reproducible.

As the title says really. I'm a new-ish Viggen driver trying to get to grips with rocket delivery. I've been following Chuck's guide and some of the better YT tutorials like Deephack and Iain Christie. And no matter what I do, my rockets always go long. Not massively long, but long enough for the unarmoured truck I'm aiming for to take no damage. I get they are not precision weapons and more of an 'area saturation' thing, so I would expect a spread of impacts around my targeted point. But I'm finding they consistently, repeatably go long. Anyone else experienced this? What might I be doing wrong? Thanks in advance!

Happened to me too, latest OB, single player MT Marianas map. Cover would not open by clicking or when bound to a button. Refuelling switch does move when bound to a button, and allows AAR when in the forward position as expected.

Will Virpil's software talk to my VKB stick?

This may or may not be a stupid question so I figure it goes here. I have the VKB T-rudder pedals - no toe brakes. I figure I can use the twist grip on my stick for differential braking. However, DCS picks up the twist as a single axis. If I assign it to the left brake and then assign it to the right brake it takes the assignment away from the left brake. Is there a way for me to tell DCS to use the Z axis of the stick from centre to fully left as the input for the left brake and from centre to full right as the input for the right brake? Or alternatively, can I set a modifier somehow that when I hold a button down it makes DCS treat my rudder pedals as toe brake input? Currently, I just use a hat on my throttle as toe brakes. It works, kinda, but it's not great.

Thank you! I was going mad clicking on everything, and then when I did it wasn’t sure how.

As the title says really. I've designated a number of TOO's with the TPOD, cued them up as targets for GBU38 and successfully dropped them. Great. Now I'd like to navigate my way back home, using waypoints. But I can't select my waypoints anymore. All the EHSI will cycle through is T0, T1 and T2. I've tried hitting DESG, hitting NWS to put the TPOD back to Snowplow or VVSLV, I've put the HUD back in NAV mode, put master arm off. I've no more weapons on the jet but it won't go back to navigating on waypoints. Right - I've somehow done it. Long press of waypoint increment, I turned the TPOD back on, and pressed NWS so it said NO DES and now wayponts are available to select again. But which of these actions, if any, is the right one to do I don't know. The AV8 is great, in those times when you're not wondering what the hell the jet is doing *that* for.