Karon

Same here. Shorter extensions but it's lightyears beyond anything I have used before (CH Fighterstick, non cheap saitek :) )!

I've spent the afternoon plugging and unplugging peripherals. Then I tried to control the rudder with the TWCS and, when the problem occurred, it got stuck as well. So I ended up thinking the problem might be something similar as the one you mentioned; although I've been flying with the central position trimmer since BS1 and never had issues before. For instance, here: I'm playing with the very same input config, no issues though. Any way, tomorrow I do some more tests.

So, yesterday I decided to format and install Win10. Today I tried and the issue happened again, I noticed that both pedals and stick axis are unresponsive, but the trigger button (on the stick) works. Log file attached. I will DC everything and plug in my stuff one by one and see what happens. EDIT: I have test my old CH Fighterstick + Pedals + Throttle only and I have the very same issue. Quite disheartening. dcs.txt

Sure, I've attached the log here (renamed to .txt). EDIT I forgot to mention that DCS was modded when I recorded, but the issue happens with no mods. dcs - 180330.txt

Yes, admin and full screen, plus windows aero disabled.

I have a really odd issue when flying the Ka-50 since the 2.5, it wasn't occurring in 2.2 (nor since BS1), my stick becomes unresponsive while flying when: - it's off-centre; - I'm holding the trimmer; - pedals are off-centre. Altough stuck in-cockpit, the stick works perfectly in the controls menu. The sticks works again as soon as I re-centre the pedals and release the trimmer. I've recorded the issue, 5'00": I've monitored my USB peripherals with USB logview and it's fine (also, I have Win 7). I have swapped ports using and avoiding USB 3.0; nothing has changed. It seems quite random although the longer I play, the more often it seems to happen. DxDiag is attached. Any ideas? DxDiag.txt

Mavs only need to be locked (and after having uncaged them + SS [↑]). The TV is automatically slaved to the TPOD once you use the TDC with the latter. Activate the TPOD on a MFD then: 1. →Standby (activates the TPOD) 2. →TDC (allows the TDC to control the TPOD) Now move it around; on the second MFD activate the DMT and you'll see that it actually follows the TPOD. You don't need the LSS mode to self-lase. Exempli gratia, for GBUs: - fist two steps as mentioned above; - 2nd MFG, select GBUs, set them up (fuse, multi/qty, etc); - activate master arm, you should already be in AG mode; - 1st MFD switch the TPOD mode to laser (it has 3 modes: training, lasing, marker); - drop the bomb (CCRP is fine); - later activate the laser, switch to the ordnance view and see it follow the laser. I can't fire up DCS now, but that should be it. I'll check later and correct. EDIT Alright, try this: Menu → TPOD Activate it and slave to TDC to it by pressing: - STBY - TDC Slew the TPOD on the target (Area/Point is currently bugged - haven't checked last patch though ) Remove the laser safe by pressing SAFE (ARMED will appear) Select the correct function, toggle between Trnl→Mrkr→LASR Set up payload and stuff on the 2nd MFD, drop and activate the laser by pressing FIRE Mavs can be used in a similar way, although they don't need to be lased (D/G/H/K; !E). You can use the TV (consider the TPOD as an enhanced TV) to find the target, uncage mav, SS [↑], RMFD should show Mav's TV view, then lock when in range and rifle. Haven't cheked in ages, but the procedure shouldn't be different (and, hopefully, I haven't forgot anything).

Thanks mate! I was thinking about the MFDs as well but I couldn't find any cool solution to "embed" them into the desk mount. Quick update: rotary encoders delivered and mounted; as soon as the caps arrive I'll open a thread in In&Out.

Some conditions must be met in order to activat the APs. Check NATOPs.

I don't have the NATOPS right now so I can't double check; but IIRC this behavious is mentioned there and I think it can also be disabled. As soon as I'm back I'll check and edit. EDIT

+1 LeCuvier I'd personally love to see more flexible controls, especially considering that the Ka-50 is my favourive module. I guess a decent solution might be using pair of controls to scroll "up and down" through the controls (RAZBAM has done the same thing with their AV-8B). Probably not the best solution for cockpit builders, but definitely handy for everyone else. That being said, as soon as I have some spare time I'll dive onto the lua files. I've just built a small button box for the Virpil desk mount and it sucks not having appropriate controls to assign to it.

You know what pisses my off about the Desk Mount? The empty space between the stick base and the desk. I thought it would be a great place for some additional controls! At first I thought about using some Microchip's PIC (I worked a lot with assembler on 8/16 bits microcontrollers) then I've found Arduino and I've discovered a whole new world (screw you single register 8-bit PIC! :D ). This is the current result, I'm waiting for the delivery of the rotary encoders (ETA end of March / beginning of April) then I'll open a proper thread in the DIY area of the forum (that's why there's so much empty space in the top box).

Easy comm is an option that makes comms, well, easier. For instance it allows you contact ATC/tanker/others from the comm menu withouth actually selecting the proper frequency. It's a work around, de facto, for modules where proper radios are still WIP. EDIT: go in the mission editor and set up some tests, you can force Easy Comms On or Off.

Hotfix 3 patch notes for Harrier are outdated and refer to previous patches: the Moving Map MFD page has been introduced weeks ago and it hasn't been updated yet. Good news though, Hotfix 3 has introduced APs functionality for the Harrier, and they actually work quite well; I guess we'll see them mentioned in HF4's patch notes.. Also, as you said "Added EHSD Moving Map (Work-in-Progress)". Some stuff might work, some might not. If it ware working you should have found pics of it all over the place :)

It sits quite back otherwise, when using extensions and pushing the stick, it (or your hand) my hit the support itself. I have the issue as yours but I just drag the monitor closer to me every time. Not the best solution, but it works well.

Moving the TPOD while lasing. It reverts to SAFE although it shoudn't.

NWS normally resets it, same as the TV. Yep, I know, HOTAS only would be much better but AFAIK that's what we have with this version of Harrier and TPOD.

It does work with DS and MSAA (tested both 8x and 4x). I have posted a pic in the TPOD thread and yes, targets are now really easy to spot (ofc it's not perfect yet but a very welcome improvement over previous versions). Controls are there, although not simulated yet.

After passing control to IRMV (in case of D/G), use the TDC action to lock. Keep in mind it doesn't lock if you are too far. As a test, keep trying until you are within a couple miles from the tgt. IIRC normally it lock at ~7nm.

I don't have the natops right now but IIRC you can only toggle between wide and narrow. I suggest you to buy a set of TM MFD. They're not too expensive but sooo good on modern NATO aircrafts and actually on any module. I guess it's intended then. I haven't tried much (I'm already back in my beloved Ka-50 in the shiny 2.5 :) ) but I don't remember anything like that. I normally have the TPOD on the L MFD and toggling between weapons in the R MFD didn't change anything in the L MFD.

You mean this "noise"? I guess they're simulating a lower quality TPOD than the latest available (and off-limits for DCS)? (sorry for the pic, it's from my streaming and I can't get a new pic right now)

The MFD function has been implemented but there's no map. IIRC that page couldn't be opened before the last patch.

I haven't tried much yet but it seems to working as it was in 1.5.8ob.

He's using both BH and WH, check the spoilers. The best part of 2.5 is not really the brightness of the vehicles but the lack of that old ubiquitous background noise. If you were used to the old FLIR then spotting in 2.5 is super easy.

That's what we see (and I guess everyone is supposed to see): As I press printscreen to get the shot the focus moves from the OBS, but you can clearly see the darker columns. Those have always been pre-assigned, I've never had to do anything. I wonder if is a problem of the Harrier or ED's.