Jedra

@Jesse - thanks for your response. I have a lot to learn! As a new owner of the G940, I applied the FW upgrade immediately and therefore have no experience of it pre-update. Anyways I will mull over your response over the next few days as I get to grips with the Black Shark. For the moment I will be happy to keep it in the air for a few minutes without a fatal dive while learning the commands or the rotor blades destroying themselves (which seems to be happening a lot!). It's all part of the learning experience!

Apologies, I am new here (a recent BS2 and G940 owner) and am trying to get up to speed with the various issues with the G940. Can I sumarise what I think are the issues that might also be affecting me... 1. You can only use Trim Lock if you have FF turned on for the stick. So, I can't use the stick in non FF mode and then get it to lock into a position I set? Is this an issues with the G940 generally or with it in combination with BS2? I have read the discussion, but I feel like I have walked into a long conversation half way through! 2. When I do put the stick into trim lock, it drops out slightly when I release the stick - almost as if the lock is still allowing a miliimeter or so of travel. Given the control is very senstive, this immediately sets me pitching up or down dramatically. Is this expected behaviour or is my stick or setup wrong? 3. Unrelated to some of the discussions here, but I can't find the actual answer anywhere else, but should I wish to use the Logitech profiler, which executable should I point it at? Launcher.exe or dcs.exe? I have managed to work out how to import profiles directly into DS2 and the stick, throttle and pedals are functioning but I am now just looking at what the profiler does that the in game stuff doesn't (if anything). Again, sorry if I am going through old ground but I could not find definitive answers anywhere and this thread looked the most likely candidate to ask in.

Hi, I am new here so please bear with my ignorance. I recently purchased Black Shark 2 and also acquired a Logitech G940 Stick, Throttle, Pedal combo. I used one of the few profiles around on the forums as I did not want to go through the process immediately of mapping all the functions (as both the simulator and the joystick were new to me). Anyway I discovered a problem with the collective control when using a LUA created in Black Shark 1. I posted this initially on the Steam forums (this one was down), so the following is a cut and paste job from there... START When you load a profile from a BS1 profile save, it stores the collective value in Action 2088. In Black Shark 2, the Collective is actually Action 2087. After loading a profile from a BS1 profile save, you will see this in the throttle LUA file... [4] = { ["combos"] = { [1] = { ["key"] = "JOY_X", ["reformers"] = { }, -- end of ["reformers"] }, -- end of [1] }, -- end of ["combos"] [b][color=red]["action"] = 2088,[/color][/b] ["name"] = "Flight Control Collective", ["category"] = "Axis Commands", }, -- end of [4] Now, no matter what mappings you change, the collective will always be assigned to 2088. This is why deleting the lua file and restarting BS2 works as when it recreates the LUA on launch it correctly maps the collective to 2087. So to resolve this, I did the following; 1. Deleted the LUA files. 2. Re started BS2. 3. Cleared all the mappings to Joystick/Throttle and Pedals (including the axis). 4. Loaded a profile from BS1 with all of the G940 button assignments. 5. Closed down BS2. 6. I then edited the throttle LUA and changed the collective mapping from 2088 to 2087... [4] = { ["combos"] = { [1] = { ["key"] = "JOY_X", ["reformers"] = { }, -- end of ["reformers"] }, -- end of [1] }, -- end of ["combos"] [b][color=red]["action"] = 2087,[/color][/b] ["name"] = "Flight Control Collective", ["category"] = "Axis Commands", }, -- end of [4] If you import a profile created in BS1, you will need to make sure that the collective Action is changed in the lua file. You can either do this in the imported file BEFORE you import it, or in the resultant BS2 LUA file after you have imported it. Hope this makes sense!! JeeseJames - thanks for your reply, it helped point me in the right direction. I just had to know why deleting the file made it work - I knew it must have been something in the LUA XML file! EDIT (again) ---> There may be other mappings that have changed, so if I spot any I will post them here. It would be good if anyone else spots some then they post too! END I am basically posting this just in case anyone else comes across the same issue.