Vakarian

This issue seems to be resolved. After few tests, non static units are now correctly travelling on the ship. It does work only for the amphibious units (likely due to the issue where non-amphibious units can't be placed on water) but it's a progress

Hi there @Flappie. Thanks for not forgetting this As far as I can see, the issue seems to be resolved. Watched the track (yeah, it is nice how it still works) and for the whole duration the IFVs were visible on the ship. We have a saying in my team at work "Due to sufficient time passage, the issue seems to have fixed itself". Pass along the thanks to the team, they must have done something to fix the rendering issue. Also, for everyone else watching. this is why we do tracks for bug reports. Might seem meaningless, but it isn't.

But the base exists already. Two versions of it.

This was recently reported, but I'm betting there are more reports like this in the history of the forum

Is there any change to get REDFOR infantry units? AFAIK, we have only basic AK and Igla dudes from REDFOR, while with your pack we have some diversity on BLUFOR side

That's the artefact of the recording, not a planned change. IIRC it happens when recording using Nvidia Shadowplay

This is happening even on 21:9 resolutions (3440x1440), it does look weird, but it also has some advantages. When flying formation, other guy is "zoomed and larger" so it's easier to keep track. Although, in all seriousness, if this could be adjusted, that would be great. Can provide whatever info is needed

You shouldn't need to if they are placed properly in the saved games folder. There will be a prompt "do you want to delete these files". If it contains just liveries, select no.

Running the repair should redownload all modified/missing files and restore original functionality

Well, yeah, that makes sense. "o'clock" positions should be matching the TSD only if it's in "track up" mode. If you set it on "North up", you are flying due west and hear "SA-8 3 o'clock", you want the it showing UP on the TSD, not on the right side as that would mean it's at your 6, not 3. You have to understand two different spatial references being in place when you put the TSD "north up" and you hear CMWS call in relation to your aircraft. They are not the same.

Yeah, that's a bit of an old news, a fact known for a while. Just wait patiently and it'll get here eventually.

Happens the same in front and back seat, here's dcs log if it helps. Easily reproduces per idenwen's instructions dcs.log

It would be a lot better if these bindings were added in by default, rather than having to rely on 3rd party mods for that (and not just for A-10...)

Nope. Leave it as it is

Wow, so simple. Honestly, I'm ashamed to tell what I've tried googling to find them only to fail miserably... Thanks a lot, found them and ordering them immediately so I don't forget.

What are your plans for the double potentiometers used for Radios 1/3 and 2/4? I've thought of designing the UFC myself, but that single item threw me off so much I thought of finding a potentiometer with a push button and just using that as a modifier

Does the app need to be in any specific folder to works properly? I'm experiencing that the options.lua filed gets messed up every time I load DCS through the updated utility (using updated version, pressed "save" button before starting). For example, I set what I want for my graphic settings in the utility, start DCS and all options are set to as low as possible. Also, it seems like authorization data got messed up too as after seeing this loss of graphics settings after using utility, I manually started the DCS using MT exe file and then I had to log in again. On a hunch I went to check the special settings and they also got restored to defaults after this... Any clue what to try next? I've checked the log file, no errors showed up (at least obvious ones)

In development

If I read the IRL throttle diagram correct, the pinky switch on the pilot's throttle should move up/down for MAN2/MAN1 countermeasures dispense. However currently in game I see that it's moving forward/backward. Nothing major, but now that I've seen it, I can't unsee it Track file showing the switch movement is attached per rules pinkySwitch.trk

It's not a control to bind, rather the button option. When you for example bind speedbrake on to "BTN_69", you can bind speedbrake off to "BTN_69_OFF". That "BTN_69_OFF" is in the dropdown menu which you need to select. That way when you move your switch to on position it will deploy the speedbrake and then when you move the switch to off position it will retract it.

Can you like stop mentioning VAICOM whenever someone posts a question about the radios and possible bugs with them? It doesn't bring anything to the table, especially when troubleshooting a bug.

Ah, thanks for clearing that out

Are you guys maybe seeing something like this?

Wow, you couldn't be more wrong.