Puma

There is nothing wrong with having “target” waypoints in a flight plan. Establishing a common naming convention will help clarify what is what. I’ll often use nav points, then CP.1 IP.1 TGT.1 as waypoint names. Toss in friendly positions too, but the risk is obvious, so ad a hint: JTAC.1XXXXXXX. I find for most missions, a single flight plan does well, but if you want to try something or handle a more complex mission or multiple options, remember you can have multiple flight plans in the A-10 CDU. So have on for ingress, one for tgt.area, on for egress and one for divert.

Thanks Bignewy. Ugh... well, I was unable to reproduce this by setting back to 48000kHz. In both settings, the log reports 1 channels with mask 0x4, then later Channel layout: FrontCenter. For what my speculation is worth, changing the default format may have nudged windows into setting the correct mask and thus resolving it for DCS. Not much DCS can be expected to do when it get reported an invalid channel mask, so this might be blamable on windows. I'll keep an eye out for future errors but at this moment, it seems to be unable to reproduce :(

Oo, found something. If i change the advanced device properties, default format from 1ch 16 bit 48kHz to 44.1kHz, the error goes away. Mask reports 0x4. A Good enough for me, but this could be handled more generally in DCS. i have a strange behaviour in the past where some flights I have headert audio and some flights it goes over my main sound. Makes me wonder if this mask can change somewhat randomly and that dcs fails because of it.

Hmm I do not have any of the usual audio configuration options for multichannel devices. What da70 driver are you using? Do you find any place in windows where you can configure the channel it is presenting as? Also worth noting I cannot use the hardcoding trick from the linked post because I also have a 5.1 device for surround. Only comms are intended to come out this device.

Amazingly similar issue, thanks for sharing!! I am on the latest open beta (2.5.6.57530). Interesting that we both have the DA70 but got different masks reporting (I got mask 0... which is not much of a mask!). I’ll explore windows speaker settings in case I can influence that.

I have an mono headset designed for communications, however when I load it, dcs.log reports the following: 2020-11-14 01:31:51.251 INFO SOUND: Opening audio device "{0.0.0.00000000}.{b09042ab-fe69-4064-b0d9-a3b9f9e053e6}" 2020-11-14 01:31:51.252 INFO SOUND: Driver reports 1 channels with mask 0x0 2020-11-14 01:31:51.252 ERROR SOUND: Driver reported an invalid output configuration! Forcing stereo output. 2020-11-14 01:31:51.252 INFO SOUND: Using 2 channels at 48000 Hz 2020-11-14 01:31:51.252 INFO SOUND: Channel layout: Headphones/Stereo 2020-11-14 01:31:51.259 ERROR SOUND: Failed to Initialize IAudioClient: 0x88890008 (AUDCLNT_E_UNSUPPORTED_FORMAT) 2020-11-14 01:31:51.259 ERROR SOUND: Failed to start aux 1 DCS should support 1 channel audio devices. My device is a USB Plantronics DA70, and a SHR2301 headset (https://www.poly.com/ca/en/products/headsets/specials/shr-2301-01).

The DCS A-10C manual pg 401 also suggests that tms-right-short should create the mark point at the hdc location, not the los crosshair.

My most frequent use case is hooking a flight member (most valuable as -2 hooking -1), so the hook info provided can assist in formation station keeping. Hooking enables display of hooked ship ground speed, which can also contribute to the picture and ensure safe rejoin speed before visual picture is established.

@Outlaw: Never seen that. Sounds to it’s time for a repair.

This is an awesome find, and such an easy optimization an I agree the changes would be imperceptible. This really should be considered a dcs bug IMO. One script to resample all these and most players in limited hardware would gain more usable vram.

They are fixed for multiplayer ie other aircraft see your lights correctly set, but your own still don’t look right to you.

I wouldn’t do it yet. There is some issue where if you don’t have -1 installed then the flight model of -2 is way wrong. Must be sharing some files atm. Likely will be fixed. Thay raises a similar question for me though: I bought the upgrade. Can I use -1 on my laptop and -2 on the sim pc?

You should be able to release the other ones. They are burned because the short pressed started a single-use battery which cannot be recharged. Try selecting the station manually on the dsms with the adjacent button?

https://forums.eagle.ru/showthread.php?t=287859

Sounds very similar. I did not go eo off and back on, but I wonder if loading twice on the ramp ends up cycling the state of the mavericks in the same way.

Has anyone else noticed the mav page code display at the top showing 1111 while the dsms page shows the selected code? I’ve had this happen on mylast two flights. Both times though I had to reload the same mav loadout on the ramp. Dsms is correct, after eo on mav is wrong. Reloading dsms inv in the air (and then waiting out eo on again) fixes it. Yesterday I’m 99% sure I rifled one mav before noticing, and it tracked... so I’m wondering if the bug is just in the mav page display, but the maverick is actually set “correctly”? If anyone else confirms, I’ll try to put a track together.

FWIW I have never enabled latching mode and this is precisely why. Admittedly I didn’t know how sever the consequences were, but it never seemed like a good idea to be one click away from accidentally lasing everything. With the tm warthog its not much hand stress.

Just confirming: did you switch the laser into latch mode before trying this? By default it is only on when pinky is held down. Tgp cntl page allows you to set that to latch mode which makes the pinky button toggle it on:off. If its not that, does your hud/tgp symbology work properly? “L” should be flashing while the laser is on.

Really well done, thanks for putting that together.

At worst, it should be possible by copying the input config files with few if any changes required other than the right folder name. Having said thay I will be pretty disappointed in ED if they dont auto migrate for you. Did blackshark 2 auto migrate??

Good analysis. I’m curious why there are two sets though? When is the [13] used vs [14]?

I’m track ir and also just move my head when I need to see something. Its’ve very natural by now, just like looking down to see the hsi, or aft for a radio. For people really suffering from this, do you have all six degrees of freedom properly mapped in trackir. I.e. can you move your head forward, up, down, left, right?

Fascinating! I wonder if dcs A-10C will recreate that connection. Would certainly make my cockpit update simpler if they do!

For dcs, the most significant change it will bring is access to a second uhf freq. Currently you are limited to one vhf-am, one uhf and one vhf-fm. With the new arc-210, single, you will have one uhf, one vhf-fm, and the arc-210 which can be uhf or vhf. Probably zero benefit for single player but for multiplayer environments with atc, range control, other flights, jtacs, afacs, etc, having more flexibility will be very nice.

So in that configuration, would it follow that the ARC-210 full head controls ARC-210-1 and -2, the ARC-164 is unchanged... and is the "current" VHF-FM ARC-186 is removed?