Terrorvogel

Hi Duckling! I have read all the nice links that you have reserarched and fiddled arround whole day with code from other users but with no result.:( Let me tell you what i have done so far: First of all, you´re right, the sioc configuration was from a very helpful user "Oldcooltronix" and the origin (i assume) is the config from user "Takeoff-For-Fun". In my ExportSupport.lua i have nothing changed so far: Edited in: P:\DCS World OpenBeta\Mods\aircraft\Ka-50\Cockpit\Scripts\clickabledata.lua When changing this, cut-off-levers still inverted (but working): arg = {554,554} to arg = {554,55} arg = {555,55} stays arg = {555,55} or arg = {554,554} stays arg = {554,554} arg = {555,55} to arg = {555,555} When deleting the complete two lines, nothing changes, cut-offs still working???: elements["EMERGENCY-BRAKE ENGINE-RIGHT-PTR"]............. elements["BRAKE-ROTOR-LOW-PTR01"].............. If temporary renaming the clickabledata.lua no switches were working anymore except the cut-off-levers??? Seems they are configured somwhere other place? This is so weird... In my SioctoDcs.lua there are this lines for cut-off-levers: [890] = {TwoPositionSwitch, 4, 9[b], 1[/b]}, -- Cut off Left Engine [900] = {TwoPositionSwitch, 4, 10[b], 1[/b]}, --Cut Off Right EngineSo i cannot add the recommended trailing ", 1" which whould invert the outcome. So i tried this but no change: [890] = {TwoPositionSwitch, 4, 9,}, -- Cut off Left Engine [900] = {TwoPositionSwitch, 4, 10,}, --Cut Off Right EngineThis link with the connection of mastercards port for synchronizing, looks very interesting. Must read in, if this is a future solution for my config. Thx for this. Learned a lot again from your explanations here:) If you are interested i could give you my "Black Shark 2 Ugrade Version". I could send you the registration code and you could keep the module because i don´t need it anymore due to buying the "full" version years ago. I don´t know how to install this one however but the code should still be active and working. But we also can bury this "cut-off-lever" issue and not wasting time anymore if you wish. I would understand that:) P.S. Will your site be up again? I´m so curious for your pit:D Regards, Terrorvogel

Hi Duckling, thx for your time! with this typo thingy, i tried out with the letter "I" but nothing changed. At this moment i tested with and without ", Type I". But no change. Last state is that i deleted the completely ", Type I" from code. Yes, your´re right, the "EMERGENCY-BRAKE ENGINE-LEFT-PTR" is a two position switch. I changed the initializing value to "1" but nothing changed. How can this be? Var 0890, name C_off_val1, Value [b]1[/b] // Value of Cut Off Left Engine switch Var 0890 is linked inside SiocToDcs.lua or siocConfig.luaOnly when changing the state inside IOCPConsole, the lever changes its state. And the strange thing is, when starting a "cold start mission", the Cut-Off-Levers staying in sync. If running "warm start", the levers immediately going out of sync. Not running Helios or something other in the background. I have taken some screenies: Cold Start Mission (synced): Cold Start Mission (synced) sending IOCPConsole 1x Value "1" Left Lever: Warm Start Mission (out of sync): In IOCPConsole log there is no event with Var 890 and 900, which could explain the state change... Warm Start Mission (out of sync) sending IOCPConsole 1x Value "0" Left Lever: Why is there different behaviour wheter running cold or warm start? Is it a bug within KA50? I´m sorry Duckling but i don´t understand what you mean with this "lotodcs.lua":cry:. What was the exact context of this? If it´s not important just ignore. Regards, Terrorvogel

Hi Duckling!!! thx again for the fast answer:) What do you mean for using a seperate Var for "switch-input" and "dcs value"? Var 0645 is the "changeable value var" and Var 6000 ist the physical opencockpits-switch. Is there a better way to seperate them? DCS:KA-50 in clickabledata.lua switches: elements["EMERGENCY-BRAKE ENGINE-LEFT-PTR"] = { class = {class_type.TUMB, class_type.TUMB}, hint = LOCALIZE("Left engine cut-off valve"), device = devices.ENGINE_INTERFACE, action = {device_commands.Button_9,device_commands.Button_9}, arg = {554,554}, arg_value = {direction*1.0,-direction*1.0}, arg_lim = {{0.0, 1.0},{0.0, 1.0}}, updatable = true, use_OBB = true} elements["EMERGENCY-BRAKE ENGINE-RIGHT-PTR"] = { class = {class_type.TUMB,class_type.TUMB}, hint = LOCALIZE("Right engine cut-off valve"), device = devices.ENGINE_INTERFACE, action = {device_commands.Button_10,device_commands.Button_10}, arg = {555,55}, arg_value = {direction*1.0,-direction*1.0}, arg_lim = {{0.0, 1.0},{0.0, 1.0}}, updatable = true, use_OBB = true} I tried to change this: arg_lim = {{0.0, 1.0},{0.0, 1.0}} to this, but nothing changes: arg_lim = {{1.0, 0.0},{1.0, 0.0}} How can i "invert" the switches "behaviour" there? What i don´t like by this way is, that every DCS update i have to change theese again to invert my Cut-offs... The ", Type 1" should be no typo i hope. At http://www.lekseecon.nl/howto.html#onoff_switch i have read, to use this command for on/off switch. Did i misunderstood something there? For getting sure, i have tested the upper code without ", Type 1" but nothing changed. What makes me wonder is, am i the only one with this "issue" or is the answer that simple and i´m too stupid to solve;) P.S. The oxygen breathing machine, you helped me so much, is nearly ready. I have spent lots of time to integrate a working pc-mike into the mask and building headphones into helmet. The only thing to finish it, is that i´m waiting for that damn relais from china, the second time now. It takes over a month each time. If it is not arriving again, im spending "more" money and buy it in my country - not worth the nerves anymore... What i can say so far is, it´s really increasing the immersion with a real working oxygen mask:) Regards

For the 3x ejecting switches i have found a solution to invert but for the Engine Cut-Off levers don´t. Here´s the working code of ONE of the three switches, for those who are interested in: Var 0645, name Ej_SW1_val, Value 0 // Value of EJECT1 switch Var 6000, name EJECT1, Link IOCARD_SW, Device 5, Input 30, Type I // SWITCH EJECT 1 { IF &EJECT1 = 1 { &Ej_SW1_val = 0 } ELSE { IF &EJECT1 = 0 { &Ej_SW1_val = 1 } } } I have tried the same code for the ONE of the two Engine Cut-Off levers but without success: Var 0890, name C_off_val1, Value 0 // Value of Cut Off Left Engine switch Var 0890 is linked inside SiocToDcs.lua or siocConfig.lua Var 6010, name C_OFF_G, Link IOCARD_SW, Input 36, Type 1 // Cut Off Left Engine { IF &C_OFF_G = 1 { &C_off_val1 = 0 } ELSE { IF &C_OFF_G = 0 { &C_off_val1 = 1 } } } When starting a DCS mission the Cut-Off lever is still shutting off allthough the new inverted values. Does anyone has a hint what is the cause of this behaviour? Here are some pictures of IOCPConsole:

Hi Guys! Does someone knows how to invert a switch in SIOC? I´m having the issue, that no matter how i solder the KA50´s Eject Seat-Sys-Switches (3x of ON-OFF with one big common cover), i´m getting still the opposite value inside DCS. I already tried this to invert this switch(es) but it doesn´t work: Var 0645, name EJECT1, Link IOCARD_SW, Device 5, Input 30, Type I // SWITCH EJECT 1 { &EJECT1 = CHANGEBITN 0 &EJECT1 } and Var 0645, name EJECT1, Link IOCARD_SW, Device 5, Input 30, Type I // SWITCH EJECT 1 { IF &EJECT1 = 0 { &EJECT1 = 1 } ELSE { &EJECT1 = 0 } } When sending manually "Value 0" in SIOC IOCP Console , the switch inside DCS moves to one time to the right "opposite" direction. Now my question is, how to invert this value permanently? It is really annoying, when switches always have to be in the "wrong" physically position to get synchonized within DCS. Really hope someone can help me out of here...:helpsmilie: P.S. Having the same issue with landing gear, cut-off-valves (two red levers) and with cockpits door. All the other switches are working as they should. Regards, Terrorvogel

+1

I will try this out. Thx so far! Regards, Terrorvogel

Hello, unfortunately the A-10's Gau rumble running with Buttkicker is still too slow. When firing 50 rounds per second in the first second and up to 70 rounds when pushing the trigger longer, there should be from the beginning a constant, very very little fluctuating signal sent to the transducer. It feels a lot better now but there should be a little tuneup in higher firerate. Now you can still feel every single bullet and this cannot be right with 50Hz up to 70Hz. Blackshark fits perfect now since last update. Is there a way to edit the the output-rate frequency by myself somewhere deep inside the Simshaker software? Regards Terrorvogel

+1

I have noted that there are two version numbers at the same time? Which one is the active one now? If i´m already on 1.1.1.42 the GAU issue is still persisting. What i also noted is when firing the KA-50´s gun, there is no difference in rumble speed between firering in low/high rate. Something seems really wrong here...

Ok my Simshaker version is 1.0.0.31 and i tested the A-10 GAU with Low/Highpass filter on and off and with buttkicker's frequenzy setting from 30Hz to full range. The result is always the same: Simshaker produces a fluctuating output instead of an expected permanent low frequent "brrrrrrrrrrrt". This makes no fun because it feels very unnatural. With this high fire rate there should be not this strong feelable "gaps" when firing the gun. I really hope Andre has a solution for this because Simshaker has no value for me if the A-10's gun feel like that. P.S. I have tested too with my second set of Buttkicker Gamer2, to check that there is no hardware issue with my transducer or amp. Regards, Terrorvogel

Hi f4l0! I'm not at home now but at the end of the weekend i can tell you the detailed frequenzy settings of my Buttkicker Gamer 2. There was an online update the last days within Simshaker and it has been applied well i believe. I will look into what exact version is installed when @home again. "Gamebreaker" was a bit exaggerated but it feels that bad that i need to deactivate the gun of the A-10 within Simshaker. Regards, Terrorvogel

The A-10's gun is still rumbling slow as WWII cannon with simshaker module. When will this be updated/patched? It is an absolutely gamebreaker when simshaker is active while using the GAU.

+1

Ka-50 seen in DCS manual: Fire control system enables the cannon rate of fire to be set to rapid (550-600 rpm) or slow (350 rpm), and it allows the burst length to be set to either 20 or 10 rounds. kind regards, Terrorvogel

Nice, can´t wait for the update:thumbup: regards, Terrorvogel

Ok, would be nice if it works. Thx so far regards, Terrorvogel

Now that this "issue" is still persisting for a long time i´d like to hear an official statement from Andre but thank you for looking into it in the future.:) Currently i need to deactivate the A-10´s gun in Simshaker due to that annoying behaviour that feels you are shooting a WWII gun. Unfortunately the "gun" is the most important thing for me inside the A-10.:D regards, Terrorvogel

This is the content firing GAU for about 3 seconds: 00:01:01.9210545 18:45:41.639 Received: p2_6_8_1~1~50~1 00:00:00.0355355 18:45:41.676 p2_6_8_1 Gun fire A10c Gain=50% 00:00:00.1257147 18:45:41.803 Received: p2_6_8_1~1~50~1 00:00:00 18:45:41.805 Skip already playing p2_6_8_1 Gun fire A10c 00:00:00.1615857 18:45:41.968 Received: p2_6_8_1~1~50~1 00:00:00.0239796 18:45:41.993 p2_6_8_1 Gun fire A10c Gain=50% 00:00:00.1373705 18:45:42.131 Received: p2_6_8_1~1~50~1 00:00:00 18:45:42.133 Skip already playing p2_6_8_1 Gun fire A10c 00:00:00.1600842 18:45:42.296 Received: p2_6_8_1~1~50~1 00:00:00.0238163 18:45:42.320 p2_6_8_1 Gun fire A10c Gain=50% 00:00:00.1391834 18:45:42.461 Received: p2_6_8_1~1~50~1 00:00:00 18:45:42.463 Skip already playing p2_6_8_1 Gun fire A10c 00:00:00.1946138 18:45:42.657 Received: p2_6_8_1~1~50~1 00:00:00.0260258 18:45:42.685 p2_6_8_1 Gun fire A10c Gain=50% 00:00:00.1356580 18:45:42.822 Received: p2_6_8_1~1~50~1 00:00:00 18:45:42.823 Skip already playing p2_6_8_1 Gun fire A10c 00:00:00.1608460 18:45:42.985 Received: p2_6_8_1~1~50~1 00:00:00.0248400 18:45:43.012 p2_6_8_1 Gun fire A10c Gain=50% 00:00:00.1365986 18:45:43.150 Received: p2_6_8_1~1~50~1 00:00:00 18:45:43.152 Skip already playing p2_6_8_1 Gun fire A10c 00:00:00.1607146 18:45:43.314 Received: p2_6_8_1~1~50~1 00:00:00.0245599 18:45:43.340 p2_6_8_1 Gun fire A10c Gain=50%

Hi Andre! I have a question due to A-10´s GAU sound with using Simshaker software together with Buttkicker. When firing the gun, the sound is fluctuating like KA-50´s gun in "slow" mode. That is a kind strange. Better would be a permanent "brrrrrrrrt" as long as the trigger is pushed. Am i doing something wrong in my settings? Everything other seems to work right... regards, Terrorvogel

Thank you Duckling for your help! I'm gonna write here again, if the breathing-machine thingy is finished to give you a feedback.:) regards, Terrorvogel

Thank you so much Duckling for your efforts!!!:thumbup: You made my day again! Now it is working fine. When switching the "real" opencockpits oxygen "on" switch, the USB outputscard has an output at the dedicated channel:) Now i have only to find the time to connect the breathing machine to this (thank of you) now working piece of software. The recommended relais is on the way from China and i will tell you when everything is finally connected but this will take some time. May i still ask you some other question? Are you using Helios and Sioc.exe together? If so, do you have a poor Helios performance too? When using this two programs together at the same time, Helios's gauges only refreshes with low 3 FPS which is very annoying and inaccurate and nearly unflyable. A friend of mine has exactly the same issue, so it is no hardware specific issue. It seems that Sioc somehow slows down Helios in the background. Oldcooltronix from forum here gave me the hint to install "Aries Radio" to get back the Helios needed performance again. There is something in the code of Aries Radio, which is overriding something so the performance is back. This is really strange. It is working so far but the problem is the dependency from "Aries" till the rest of our lifes and the unwanted korrellation with other radios like "UR Radio" etc. This whole issue seems only with opencockpits hardware in combination with Sioc.exe and Helios and not with using Arduino boards only. Would be great if you could give a hint in some direction:smartass: regards, Terrorvogel

Seems to work so far but now i got this error: Phase 2 ERROR! - Command outside place Line: 804 Var 9605, name Oxy_Power, Link IOCARD_OUT, device 3, Output 0 // Opencockpits-USB-Outputscard Power-Relay (12V-to-220V) ON/OFF ==> 9605 Var 1035, name OXY_LOW // Warning indicator OXY_LOW Dev 0 Arg 487 // Out of line !!! Var 8000, name OxygenVol // VAR for Oxygen Volume 274 Env panel // Value in SIOC 0-500 (Oxy tank is 5 liter but can't say if the emergency bottle is handled within DCS) Var 8001, name OxyPress // VAR for Oxygen Press 604 OXY panel // Value 0-1000 ( when going sub 0.5 PSI the OXY LOW caution light will popup) Var 8002, name BreathFlow // VAR for Oxygen Press 600 { IF &BreathFlow = 1 { &OXY_IND = 1 } IF &BreathFlow = 0 { &OXY_IND = 0 } } Var 9600, name OXY_IND, Link IOCARD_OUT, Output 49 // OXY Sys FLOW INDICATOR Var 9601, name Oxy_Gen, Link IOCARD_SW, Input 23 // PTR-OXYGENCP-SUPPLY (Switch in DCS: Oxygen Supply On/Off) { IF &Oxy_Gen = 1 { IF &OXY_LOW = 0 { &Oxy_Power = 1 } IF &OXY_LOW = 1 { &Oxy_Power = 0 } IF &Oxy_Gen = 0 { &Oxy_Power = 0 } } Var 9605, name Oxy_Power, Link IOCARD_OUT, device 3, Output 0 // Opencockpits-USB-Outputscard Power-Relay (12V-to-220V) ON/OFFI can´t see any issues to that line... Sorry for the circumstances! regards, Terrorvogel

Hi Duckling, nice to have you here again!:) Thanks for the detailed description and uploading your files! I have adjusted the files so far but unfortunately i still can´t compile the A-10.ssi file due to same errormessage: Phase 2 ERROR! - Command outside place Line: 783 Var 9600, name OXY_IND, Link IOCARD_OUT, Output 49 // OXY Sys FLOW INDICATOR ==> 9600 Var 1035, name OXY_LOW // Warning indicator OXY_LOW Dev 0 Arg 487 // Out of line !!! Var 8000, name OxygenVol // VAR for Oxygen Volume 274 Env panel // Value in SIOC 0-500 (Oxy tank is 5 liter but can't say if the emergency bottle is handled within DCS) Var 8001, name OxyPress // VAR for Oxygen Press 604 OXY panel // Value 0-1000 ( when going sub 0.5 PSI the OXY LOW caution light will popup) Var 8002, name BreathFlow // VAR for Oxygen Press 600 { IF &BreathFlow = 1 { &OXY_IND = 1 } IF &BreathFlow = 0 { &OXY_IND = 0 } Var 9600, name OXY_IND, Link IOCARD_OUT, Output 49 // OXY Sys FLOW INDICATOR Var 9601, name Oxy_Gen, Link IOCARD_SW, Input 23 // PTR-OXYGENCP-SUPPLY (Switch in DCS: Oxygen Supply On/Off) { IF &Oxy_Gen = 1 { IF &OXY_LOW = 0 { &Oxy_Power = 1 } IF &OXY_LOW = 1 { &Oxy_Power = 0 } IF &Oxy_Gen = 0 { &Oxy_Power = 0 } Var 9605, name Oxy_Power, Link IOCARD_OUT, device 3, Output 0 // Opencockpits-USB-Outputscard Power-Relay (12V-to-220V) ON/OFFWhat is the problem here?:huh: regards, Terrorvogel

When trying to compile the .ssi i´m getting this errormessage: ERROR! - Command outside place Line: 782 Var 9600, name OXY_Sys_FL_IND, Link IOCARD_OUT, Output 49 // OXY Sys FLOW INDICATOR ==> 9600 What does this error mean? And in this part the "&"´s are missing i believe: Var 8002, name BreathFlow // VAR for Oxygen Press 600 { IF &BreathFlow = 1 { OXY_Sys_FL_IND = 1 } IF &BreathFlow = 0 { OXY_Sys_FL_IND = 0 } So it has to look like this? Is this right???: Var 8002, name BreathFlow // VAR for Oxygen Press 600 { IF &BreathFlow = 1 { &OXY_Sys_FL_IND = 1 } IF &BreathFlow = 0 { &OXY_Sys_FL_IND = 0 }