tietze

I wonder if it is a coincidence that DCS rhymes with mess? ;-) Keep up the good work!

Sorry if this has been tried before, but I was just wondering if the "swapaxes" declaration of the forcefeedback section in the device profile could do something to change this? For example the start of my device profile looks like this: C:\Users\[username]\Saved Games\DCS\Config\Input\ka-50\joystick\Thrustmaster Combined {....}.lua function layout() return { forceFeedback = { trimmer = 1, shake = 0.5, swapAxes = false, }, keyCommands = { ...<snip>

Have you or anyone else figured out if this is actually the case? I mean it is possible to configure: Ins Weapons Status and Control Panel PUI-800 Burst length - long Burst length - short Ins Countermeasures dispensers UV-26 UV-26 Select Both boards UV-26 Select Left board UV-26 Select Right board By using the following lines to bind buttons: {combos = {{key = "JOY_BTN1"}, }, down = 3004, up = 3004, cockpit_device_id = 12, value_down = 0.2, value_up = 0.1, name = "Burst length - long", category = "Ins Weapons Status and Control Panel PUI-800"}, {combos = {{key = "JOY_BTN2"}, }, down = 3004, up = 3004, cockpit_device_id = 12, value_down = 0, value_up = 0.1, name = "Burst length - short", category = "Ins Weapons Status and Control Panel PUI-800"}, {combos = {{key = "JOY_BTN5"}, }, down = 3001, cockpit_device_id = 22, value_down = 0.1, name = "UV-26 Select Both boards", category = "Ins Countermeasures dispensers UV-26"}, {combos = {{key = "JOY_BTN3"}, }, down = 3001, cockpit_device_id = 22, value_down = 0, name = "UV-26 Select Left board", category = "Ins Countermeasures dispensers UV-26"}, {combos = {{key = "JOY_BTN4"}, }, down = 3002, cockpit_device_id = 22, value_down = 0.2, name = "UV-26 Select Right board", category = "Ins Countermeasures dispensers UV-26"}, I guess it is possible to find cockpit_device_id's here: C:\Program Files\Eagle Dynamics\DCS World\Mods\aircrafts\Ka-50\Cockpit\Scripts\devices.lua And: C:\Program Files\Eagle Dynamics\DCS World\Mods\aircrafts\Ka-50\Cockpit\Scripts\command_defs.lua Taking a look at line 691-694 of the command_defs.lua, buttons on a panel (device_commands) seems to be numbered from 3001 and up to 3050. But where those numbers are defined I have not found out yet... Controlling burst mode is done with device_command 3004 and values 0, 0.1 and 0.2. As you can see on lines 1-2 in the code above you can assign values to joystick buttons, when it is going up and down. In this way you can make the FLAPS-switch on the TM WH Throttle control burst lenght (as it was configured by default back in Black Shark 2 with TM WH connected): Upper position: long burst lenght (value=0.2) Middle: middle burst lenght (value=0.1) Down: short burst length (value=0)

In Black Shark 2 connecting a Thrustmaster Warthog would open up special possibilities for key bindings, as sketched here. Ins Weapons Status and Control Panel PUI-800 Burst length - long Burst length - short Ins Countermeasures dispensers UV-26 UV-26 Select Both boards UV-26 Select Left board UV-26 Select Right board It is possible to open up for those key bindings in DCS World by copying a device profile that contains those bindings (code shown below, same as the one linked in my signature). In other words it is not a limitation of the DCS software. If things were documented I would expect it to be quite easy to program this. But I haven't found this documentation yet - and not yet tinkered enough with it to figure everything out. I do not expect the DCS controller configuration software to enable such advanced bindings. When that is said, I guess you can find the cockpit_device_id's here: C:\Program Files\Eagle Dynamics\DCS World\Mods\aircrafts\Ka-50\Cockpit\Scripts\devices.lua And: C:\Program Files\Eagle Dynamics\DCS World\Mods\aircrafts\Ka-50\Cockpit\Scripts\command_defs.lua Taking a look at line 691-694, buttons on the panel (device_commands) seems to be numbered from 3001 and up to 3050. Controlling burst mode is done with device_command 3004 and values 0, 0.1 and 0.2. As you can see on line 9-10 in the code below you can assign values to joystick buttons, when it is going up and down. In this way you can make the FLAPS-switch on the TM WH Throttle control burst lenght: Upper position: long burst lenght (value=0.2) Middle: middle burst lenght (value=0.1) Down: short burst length (value=0) Device profile.lua: function layout() return { forceFeedback = { trimmer = 1, shake = 0.5, swapAxes = false, }, keyCommands = { {combos = {{key = "JOY_BTN1"}, }, down = 3004, up = 3004, cockpit_device_id = 12, value_down = 0.2, value_up = 0.1, name = "Burst length - long", category = "Ins Weapons Status and Control Panel PUI-800"}, {combos = {{key = "JOY_BTN2"}, }, down = 3004, up = 3004, cockpit_device_id = 12, value_down = 0, value_up = 0.1, name = "Burst length - short", category = "Ins Weapons Status and Control Panel PUI-800"}, {combos = {{key = "JOY_BTN6"}, }, down = iCommandPlaneFire, up = iCommandPlaneFireOff, name = "Gun fire", category = "Ins Cyclic Stick"}, {combos = {{key = "JOY_BTN7"}, }, down = iCommandPlanePickleOn, up = iCommandPlanePickleOff, name = "Release weapons", category = "Ins Cyclic Stick"}, {combos = {{key = "JOY_BTN5"}, }, down = 3001, cockpit_device_id = 22, value_down = 0.1, name = "UV-26 Select Both boards", category = "Ins Countermeasures dispensers UV-26"}, {combos = {{key = "JOY_BTN3"}, }, down = 3001, cockpit_device_id = 22, value_down = 0, name = "UV-26 Select Left board", category = "Ins Countermeasures dispensers UV-26"}, {combos = {{key = "JOY_BTN4"}, }, down = 3002, cockpit_device_id = 22, value_down = 0.2, name = "UV-26 Select Right board", category = "Ins Countermeasures dispensers UV-26"}, }, axisCommands = { {combos = {{key = "JOY_RX"}, }, action = iCommandPlaneSelecterHorizontalAbs, name = "Absolute SHKVAL Horizontal Slew"}, {combos = {{key = "JOY_RY"}, }, action = iCommandPlaneSelecterVerticalAbs, name = "Absolute SHKVAL Vertical Slew"}, {combos = {{key = "JOY_SLIDER1"}, }, action = iCommandPlaneCollective, name = "Flight Control Collective"}, {combos = {{key = "JOY_Y"}, }, action = iCommandPlanePitch, name = "Flight Control Cyclic Pitch"}, {combos = {{key = "JOY_X"}, }, action = iCommandPlaneRoll, name = "Flight Control Cyclic Roll"}, {combos = {{key = "JOY_SLIDER2"}, }, action = iCommandViewZoomAbs, name = "Zoom View"}, }, } end

I rarely shop around in different modules, but usually have a good idea about what I want to fly before I launch multiplayer. But how can it be harder than choosing another TARGET script? Using TARGET software is more cumbersome, but due to the sloppy DCS GUI for setting up controllers and the continuous stream of bugs and instabilities in the software I prefer to rely on TARGET scripts for the time being. In addition to being a stable platform for setting up controls for the sim, and it gives possibilities for macros and customizing curves in a way that suits me ;) I do not disagree that TARGET is not the "best idea", but it gives you much more options for customizing the joystick axis curve - provided you use the "SetCustomCurve()" as done in the linked script.

Great, keep up the good work! :-)

Have tried not to turn off Aero? In my case it just seems to work better.

Do you use more than one monitor? (if so: have you remembered to untick full screen and not disable AERO?) You could try to rename/ move the following two directories. But please note that all you settings, missions and so on will reside in the DCS folder in the Saved Games folder. Rename/ move/ delete: C:\Users\username\AppData\Local\Temp\DCS Rename/ move/ delete: C:\Users\username\Saved Games\DCS

Ranting helps none. But the guy has a point: this is a flight simulator and the control stick is quite important. If you look at a computer a joystick might be periphery. When you look at a flight simulator the joystick is not. To say that it is only natural to prioritize bugs that effect oneself is not helping anyone. And no I do not use a force feedback joystick. Instead I'm trying to figure out how and where bugfixing is going on.

I just want to confirm that this bug still exists in the KA-50 module for DCS World 1.2.2.

While Jesus had a lot of fun with parables you might want to spell-out the meaning to foster further discussion, understanding and so on.

You are missing a semicolon after the height variable.

Had this problem as well, but with the proper configuration of the GUI-area the communications menu has entered the main screen again :-) Add this to your monitorsetup (evt. removing the UIMainView statement that might already be present and entering proper width and height dimensions): Gui = { x = 0; y = 0; width = 1920; height = 1080; } UIMainView = Gui The hint by PeterP was found here: http://forums.eagle.ru/showthread.php?t=84270

Hi, sorry for the wait - I've been a bit away from simming, but just had a session with the stick and apparently the grease still performs :-)

My profile and documentation of it is available here (or my signature): http://dl.dropbox.com/u/2910357/fsim/Docs/KA-50-HOTAS_setup.pdf

Ok, I grew tired of not being able to use all keys in KA-50 in DCS World, so I copied my complete setup from Black Shark 2 to DCS World. Copied the contents of (using notepad 2): C:\Users\username\Saved Games\DCS BlackShark 2\Config\Input\ka-50\joystick\Thrustmaster Combined {0F4A3A00-BAE7-11e1-8002-444553540000}.lua Pasted the contents into the following file an saved: C:\Users\username\Saved Games\DCS\Config\Input\ka-50\joystick\Thrustmaster Combined {0F4A3A00-BAE7-11e1-8002-444553540000}.lua The only change in key-settings between Black Shark 2 and DCS World/ KA-50 is that "Blade tip lights" (R_ALT+j) has become "jump to this aircraft". The new shortcut for blade tip lights is R_CTL+R_ALT+j. Nb. the lua file is included in the controller setup in my sig :-) Nb. Nb. found info and howto: http://forums.eagle.ru/showthread.php?t=89226#16

Sorry for the delay, but I'm currently out sailing and the connection is not very good. The lucky poster is number #7 :-)

Hi, inspired by this guy I have a spare upgrade license for a Black Shark 2 upgrade (English download version) and it is up for grabs. Post before Friday 2000 (GMT+1) and a random post will be chosen. It is then possible to have the serial number relinked to that persons digitalcombasimulator account. Good luck!

I must admit I've always found the configuration interface a bit cumbersome. At least we can only hope that a more consistent behaviour will be introduced in DCS World :-)

Nb. found info and howto: http://forums.eagle.ru/showthread.php?t=89226#16 Being blessed with a harddisk crash and the following reconfiguration of controllers I've noticed an odd bug or feature in relation to controller setup. I don't know if it is common knowledge, but attaching a Thrustmaster Warthog HOTAS enables more features in Black Shark 2 for binding keys and or buttons (procedure below). For me this raises the following questions: How do I enable them in DCS World? How do I enable all possibilties for binding keys and buttons - and not just the KA-50? What about people not having this controller but still want these functionalities? Bug or feature? ;-) Procedure in Black Shark 2 When the Thrustmaster Warthog HOTAS is connected and identified by Black Shark 2 new possibilities for binding keys and buttons appear. As an example is the possibilities listed in countermeasures, before the HOTAS is connected: With the HOTAS connected it looks like this: If I save this configuration by clicking OK. These functionalities also appear when the HOTAS is connected through TARGET. But it is not possible to use them: To be able to use these functionalities you have to "Clear category", afterwards it will look like this: As far as I have seen this enables at least the stuff below for the KA-50. So my (big) question is now: how can I enable all possibilities (for all planes, not just BS)? INS Countermeasures * UV-26 Select Both Boards * UV-26 Select Left Board * UV-26 Select Right Board INS Weapons Status * Burst Length Long * Burst Length Short

Oh I meant if you had the latest old version for BS2&WH, the latest one I've got is version 6.4 :-)

Great missions - have had a lot of fun in BS2 with those! While the latest DCS version is "world" is it still possible to find and download the latest BS2 missionpack from somewhere - should one register on the STP forum? :-)

Thanks - I was just assuming I had forgotten something stupid :joystick: Track is here: https://dl.dropbox.com/u/2910357/fsim/Threads/ED%20-%20broken%20engine/starter.7z I have just installed DCS World and the P51D module. Chose instant action/ Cold Start Vaziani. Tried to delete the DCS folder, to recreate config files. Tried to remove all controllers. Still this annoying noise as recorded above and probably also to be heard in the above track.

Sorry for the double post, here is the audio: https://dl.dropbox.com/u/2910357/fsim/Threads/ED%20-%20broken%20engine/Built-in%20Input-%20Digital%20In%2020120614%201821.mp3 [mission: instant action/ Cold Start Vaziani, you can hear the SU-25T starting up in the background]

Well didn't notice until now, but it is not the P-51D that starts up and shuts down as I thought it was. Hmmm. But still there is a sound all the time like the starter is running.