Karon

Mate, it's plug and play, there's nothing to do: they're automatically recognized and bound to the appropriate in-game equivalent. You can't even change them directly. If that's not the case for you, then there's something wrong on your side. I don't where to get the cfg files, but if you find the path and I'll upload them tomorrow (going to sleep now :) ).

Folks, AFAIK they're still working on the FM. What's the point of implementing APs (that, I imagine, should intervene on the FM itself) if it is still WIP? Look, I don't mean to be rude, but this is a pre-release, feature will come when they are ready. Have a bit of patience :)

Considering how much is crap of duty + similar recycled rubbish that comes every year, well, 80$ sounds almost cheap to me :) I don't get why we get 16$ bonus though. Feel free to disagree, the gustibus.

No worries mate, you've already a great job with this tool :) So, I somehow managed to make it work this morning but it's not replicable: I've set up the BIOS, created a profile for the Ka-50 and it wasn't working. I switched back to key emulator and it was working: I set up a new profile, assigned the keys and saved it. I then closed it, done the whole procedure again but it wasn't working anymore. Anyway, with that profile I can use the TPM just fine.

Eureka, I found the error log file! :) 29.12.2017 08:29:57 version : 2.1.702.3552 2081 Custom message = [] System.Exception Failed to locate which textbox is focused. in DCSFlightpanels.TPMPanelUserControl.TextBoxContextMenuOpening(Object sender, ContextMenuEventArgs e) 29.12.2017 08:30:03 version : 2.1.702.3552 2061 Custom message = [] System.Exception Failed to locate which textbox is focused. in DCSFlightpanels.TPMPanelUserControl.TextBoxContextMenuIsVisibleChanged(Object sender, DependencyPropertyChangedEventArgs e) 29.12.2017 08:30:07 version : 2.1.702.3552 2081 Custom message = [] System.Exception Failed to locate which textbox is focused. in DCSFlightpanels.TPMPanelUserControl.TextBoxContextMenuOpening(Object sender, ContextMenuEventArgs e) 29.12.2017 08:30:08 version : 2.1.702.3552 2061 Custom message = [] System.Exception Failed to locate which textbox is focused. in DCSFlightpanels.TPMPanelUserControl.TextBoxContextMenuIsVisibleChanged(Object sender, DependencyPropertyChangedEventArgs e)I hope this can help!

Where do I find this option? Speaking of DCS, I bought a new SSD two days ago and reinstalled both DCS Open Alpha and Beta. I don't remember defining it's location though. EDIT: nvm, found it. I have managed to access the options by creating a new profile (anyone DCS bios based works 'cause I don't have it hence it stops the program). I have unchecked it but the issue persists. EDIT2: I found the config files and deleted them. Still not working. This is my cfg at the moment: <?xml version="1.0" encoding="utf-8"?> <configuration> <configSections> <sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" > <section name="DCSFlightpanels.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" /> </sectionGroup> </configSections> <userSettings> <DCSFlightpanels.Properties.Settings> <setting name="MainWindowLeft" serializeAs="String"> <value>460</value> </setting> <setting name="MainWindowTop" serializeAs="String"> <value>145</value> </setting> <setting name="MainWindowHeight" serializeAs="String"> <value>750</value> </setting> <setting name="MainWindowWidth" serializeAs="String"> <value>1000</value> </setting> <setting name="LastProfileFileUsed" serializeAs="String"> <value /> </setting> <setting name="ProcessPriority" serializeAs="String"> <value>Normal</value> </setting> </DCSFlightpanels.Properties.Settings> </userSettings> </configuration>

No, I bought it 5-6 years ago. It has been at my parent's place until last week.

I think there's a memory leak somewhere. I have tried to unplug and change the USB port, same issues.

I have streamed my desktop, it's still processing the video:

Yep, I have tried running it as standard user or admin. No success unfortunately. I can quickly record my desktop to show you what happens if you want. I imagined that :)

I have no profile, I deleted it while looking for a solution (there are 9 buttons on the TPM, re-doing the profile it's not a big deal). This is the content of an empty one, though (almost nothing but comments): Also, DCS FP tries to connect to 192.30.253.117:443 every time I open it, is that normal? I have update .net framework just in case but nothing has changed; is there anything else I might try to update?

Hey there, I have a problem with DCS FlightPanels. I have a TPM so I'm using only the key emulator. Last time I set up the profile for the Harrier it was running fine. Today I have a weird issue: basically the window's focus is always taken by the Log listbox, so I can't open menus or set up new keybinds. Whatever key a press on the keyboard, it appers in the Log box. If I press File, Options or Help the drop menu immediately disappears. Same if I left-click on any control text box. If I right click there I get two msgboxes with the following errors: 2081 Failed to locate which textbox is focused. 2061 Failed to locate which textbox is focused. Honestly no idea what's the issue. I have tried updating DCS FP, reinstalling, restarting, unplugging other devices. In-game it works properly and seems to be a GUI's problem. Odd indeed.

Here. My beloved Ka-50 in DCS 1.5.7. Nothing fancy, these are my first tests with the T-50. I've recorded them to show it to my friends so they are simple and dirty recording from a stream. This is DCS 2.2 and the Normandy map. Again, first tests so I missed the CCRP and did an awful landing but again, it's just a test. To be honest I have a lot of issues with the T-50 and the Harrier because I set both springs to almost zero traction and they are wonderful on the Ka-50, but they give me some overcorrection issues on the Harrier, especially during AAR. Tighting the springs or reverting them to medium would definitely help but I'm mainly a rotor-head :) Now I just need a new throttle. The TWCS is great money-wise but a disappointment compared to my old CH Pro Throttle. I'm kinda sad about the delay, especially for the reason that brought it (LEDs?) but I'm confidant in Virpil @Cyph3r: mate, as you can read from the comments to my first video, I've somehow managed to help selling a T-50. Can I have a free throttle now? :D:D

Correct path is: X:\Users\<username>\Saved Games\DCS\Liveries\AV8BNA If doesn't exist, create it.

As you say, it's a poket guide not a complete and polished manual..

Tthat's unusual. To be fair I had a similar issue but was due to a vertical USB port on the fron of my case. Virpil's USB plug is quite tall and I expected that port to be an issues. Plugged it in the back of my case, zero problems since.

Default is medium springs (I have immediately changed mine to light) + soft cams. Same here about the throttle. Can't wait to see some in-depth preview.

The cams in the picture above are mine. Base #201 so I can image that every base released later has the same quality. My issue with the sensor/connector has been fixed last week. I have contacted one of Virpil's engineer and they immediately shipped a pair of connectors and sensors. Arrived in a week, it took 10 minutes to change it (1 minute to open, close and change the sensor - 9 minutes to remount the PCB :S ) and now is perfect. Some pics of the surgery. Before: Sensor and connector replaced: Surgery completed! Great response time by Virpil, now I just have to persuade my wife to let me buying their throttle :)

A quick one for Zeus&Team: do you have any news about the APKWS? Last time I checked (r/hoggit) it was being developed by ED / common effort. Thanks!

Well, tbh most of those Vs seem random in the video posted before. We know they are not, but they look so. An acceptable solution, imo, is adding a certain degree of randomness even for the targets they are actually active (maybe considering the distance from the target or other parameters, that's up to the devs). In other words, I agree on having some false positive if they are generated following a credible criteria.

Probably because they have a very open approach to the community so whenever there's a problem we speak about it because maybe someone else has already found a solution. Also, CS responsiveness is great. That being said, they had issues with rough cams initially but now they fixed it (I posted a picture of mine in post #1482 and they look polished and well made). Several other issues (calibration, for instance) are due to the lack of a software but afaik is coming. Hopefully mine is simply another software issue.

These are the cams I have received, they look good although I haven't tried to mount them because I'm ok with the default ones at the moment. What are those cams, btw? No centre and hard centre, is that correct? Mine is quite silent, sometimes it "clanks" when I roll hard but that's it. It doesn't affect the movement or the input at all. I had no problems with my T-50 until few hours ago when the X axis stopped working entiraly. I fire DXTweak and I saw no input at all. I remembered when I have changed the springs that one of the connector was in bad shape and I think that might be the issue: It doens't look interrupted or different than how it was few days ago but I can't image what else went wrong. Kinda sucks, I joined a multiplayer server for the first time in years and I really wanted to stream tonight :(

I know that but as soon as I press next and get to the TWCS, it crashed. Anyway, I just need to press a button on my USB hub to DC it so it's not a big deal. I have attached two shots from DXTweaks when I don't press the Z axis (same status until I hit the 50% of the possible movement) and then fully pressed. Do you have similar results?

I tried but DXTweak crashes as soon as it selects the TWCS throttle and it always comes before the T-50. Hold on. Idea. I have unplugged the TWCS, ok now it works :D The raw for Z axis is all the way to the right instead of in the middle of the scale (which I understand since it's a break axis, not a pitch/roll). The red chevron starts moving when pull until I hit ~50% of the axis hence the value in DXTweak moves between 2095 and 4095; whereas is between 0 and 4095 for the other axis. Is that a limitation of DXTweak? EDIT: as a temporary solution I have set: min 2106, mid 3100, max 4095. It works quite well.

Nice documentary, thanks mate.