kaltokri

Ok, I did some more tests. I added a virtual sound card to my server. Because our vm cannot add a sound card, I used a software. If you need it too google "e2eSoft VSC". Then I was able to use ADF in my A-10C on dedicated server. But on my second try it didn't work again. I was confused. I realised if the mission is started fresh and I am the first player which joins the mission ADF works. But if I unpause the mission and join later ADF doesn't work. So it seams to be related to a start trigger. As a workaround I set alle ADF units to late activation and activate them with a F10 radio trigger. Now I can join the unpaused mission and ADF starts working after I run the radio call. I need to test it with multiple people later. ED, please make ADF easier and stable to use! Best regards, kaltokri

Some more lua code for Ka-50 and the Virpil VPC SharKa-50: {down = 3014, cockpit_device_id = 12, value_down = 0.0, name = _('Weapon system mode MOV'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3014, cockpit_device_id = 12, value_down = 0.1, name = _('Weapon system mode FIX'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3014, cockpit_device_id = 12, value_down = 0.2, name = _('Weapon system mode MAN'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3014, cockpit_device_id = 12, value_down = 0.3, name = _('Weapon system mode FAIL'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3014, cockpit_device_id = 12, value_down = 0.4, name = _('Weapon system mode NAV'), category = _('Ins Targeting Mode Controls Panel PVR')}, -- Engines Start-Up Control Panel {down = 3012, cockpit_device_id = 4, value_down = 0.0, name = _('Engine Startup selector START'), category = _('Ins Engines start-up control panel and levers')}, {down = 3012, cockpit_device_id = 4, value_down = 0.1, name = _('Engine Startup selector CRANK'), category = _('Ins Engines start-up control panel and levers')}, {down = 3012, cockpit_device_id = 4, value_down = 0.2, name = _('Engine Startup selector FALSE'), category = _('Ins Engines start-up control panel and levers')}, {down = 3012, up = 3012, value_down = 0.0, value_up = 0.1, cockpit_device_id = 4, name = _('Engine Startup selector START/CRANK'), category = _('Ins Engines start-up control panel and levers')}, {down = 3012, up = 3012, value_down = 0.2, value_up = 0.1, cockpit_device_id = 4, name = _('Engine Startup selector CRANK/FALSE'), category = _('Ins Engines start-up control panel and levers')}, {down = 3008, cockpit_device_id = 4, value_down = 0.15, name = _('Engine selector LEFT'), category = _('Ins Engines start-up control panel and levers')}, {down = 3008, cockpit_device_id = 4, value_down = 0.2, name = _('Engine selector RIGHT'), category = _('Ins Engines start-up control panel and levers')}, {down = 3008, cockpit_device_id = 4, value_down = 0.0, name = _('Engine selector MIDDLE'), category = _('Ins Engines start-up control panel and levers')}, {down = 3008, cockpit_device_id = 4, value_down = 0.1, name = _('Engine selector APU'), category = _('Ins Engines start-up control panel and levers')}, {down = 3008, up = 3008, value_down = 0.15, value_up = 0.0, cockpit_device_id = 4, name = _('Engine selector LEFT/MIDDLE'), category = _('Ins Engines start-up control panel and levers')}, {down = 3008, up = 3008, value_down = 0.2, value_up = 0.0, cockpit_device_id = 4, name = _('Engine selector RIGHT/MIDDLE'), category = _('Ins Engines start-up control panel and levers')},

Here is the lua code for On/On-Switches for the 3 Virpil VPC SharKa-50 Switches (HMS, AUTO/TS & LASER) to use it for the same switches in the KA-50: {down = 3002, cockpit_device_id = 23, value_down = 1.0, name = _('Helmet-mounted sight ON'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3002, cockpit_device_id = 23, value_down = 0.0, name = _('Helmet-mounted sight OFF'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3017, cockpit_device_id = 12, value_down = 1.0, name = _('Automatic tracking/gun sight AUTO'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3017, cockpit_device_id = 12, value_down = 0.0, name = _('Automatic tracking/gun sight TS'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3001, cockpit_device_id = 11, value_down = 1.0, name = _('Laser standby switch ON'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3001, cockpit_device_id = 11, value_down = 0.0, name = _('Laser standby switch OFF'), category = _('Ins Targeting Mode Controls Panel PVR')},

I started to create lua files to use the Virpil VPC SharKa-50 Panel in the Ka-50. Here are the lines for the first 4 switches at the bottom of the VPC Panel, which are placed on the PUI-800 Weapons Control Panel and also the Master Arm Switch. They are created as On/ON and On/On/On Switches. So they are also useable for simple button boxes. Hope it helps. -- PUI-800 Weapons Control Panel {down = 3001, cockpit_device_id = 12, value_down = 1.0, name = _('Master ARM On'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3001, cockpit_device_id = 12, value_down = 0.0, name = _('Master ARM Off'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3020, cockpit_device_id = 12, value_down = 1.0, name = _('Cannon rate of fire LOW'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3020, cockpit_device_id = 12, value_down = 0.0, name = _('Cannon rate of fire HIGH'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3006, cockpit_device_id = 12, value_down = 1.0, name = _('Cannon round selector switch HE'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3006, cockpit_device_id = 12, value_down = 0.0, name = _('Cannon round selector switch AP'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3004, cockpit_device_id = 12, value_down = 0.2, name = _('Weapon Burst Length LNG'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3004, cockpit_device_id = 12, value_down = 0.1, name = _('Weapon Burst Length MD'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3004, cockpit_device_id = 12, value_down = 0.0, name = _('Weapon Burst Length SHORT'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3005, cockpit_device_id = 12, value_down = 1.0, name = _('Weapon Control MAN'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3005, cockpit_device_id = 12, value_down = 0.0, name = _('Weapon Control AUTO'), category = _('Ins Weapons Status and Control Panel PUI-800')},

Hi, I want to train our students ADF navigation in the A-10C and A-10CII. I've created a mission on Caucasus with a M1A2 tank which works as ADF sender. If I start the mission on my local computer it work perfect. But if it runs on our dedicated server ADF doesn't work. I think it is related to the audio file (.ogg) which is added as radio call. Without a soundfile ADF does not work. And I've heard the dedicated server has problems with audio in other aspects, too. Can you please fix it. Maybe ADF can be changed in a way to work without audio files. Best regards, Kal PS: If you want the mission I can upload it here or elsewhere.

I've figured out how to do the A-10C battery switch on a On/On Switch for the Virpil Throttle. And the A-10C Canopy Open/Close on a On/Off/On Switch for the Virpil Panel. Maybe it helps someone else, too. Here lua code for default.lua: {down = 3006, up = 3006, value_down = 1.0, value_up = 0.5, cockpit_device_id = 39, name = _('Canopy Open'), category = _('Systems')}, {down = 3007, up = 3007, value_down = 0.0, value_up = 0.5, cockpit_device_id = 39, name = _('Canopy Close'), category = _('Systems')}, {down = 3006, cockpit_device_id = 1, value_down = 1.0, name = _('Battery ON'), category = _('Electrical power control panel')}, {down = 3006, cockpit_device_id = 1, value_down = 0.0, name = _('Battery OFF'), category = _('Electrical power control panel')},

You should try to rename the settings folder. It is somewhere in %appdata%. I'm not at my private pc. So I'm unable to post the exact path. Take a look at the first post in section Troubleshooting.

How about "fire up APU, APU Gen and contact ..."

I did the beginning of the mission three times, until I remeber to start APU Generator. I think a little bit more instruction here will help a lot of players. But it is impossible in advance to consider and catch all the mistakes a player can make. Good work Baltic!

After these two radio calls it gets a little bit confusing. The radio messages were barely understandable. I manage to land, but the ingress call came after the contact ground. I think I did something wrong, but here the player should be guided a little more precisely about Frequency and what to do. 4:05:45.870 [PLAYER] Tusk 1-1, wilco. 4:05:36.870 [TONOPAH TTR - SILVERBOW] Tusk 1-1, Silverbow, contact Tower when 5 miles out. Thanks for your work! The campaigns is worth every penny. Needs only some little tweaks. But I thing a newbies will be overwhelmed.

After 2 hours I understand the guide of LeCuvier. Thank you very much! Here lua code for default.lua: JTRS & CICU as single button commands or ON/OFF toggle if someone needs it: -- JTRS On & Off for push buttons {down = 3009, cockpit_device_id = 7, value_down = 1.0, name = _('JTRS ON'), category = _('Armament HUD Control Panel')}, {down = 3009, cockpit_device_id = 7, value_down = 0.0, name = _('JTRS OFF'), category = _('Armament HUD Control Panel')}, -- JTRS On/Off for a ON/OFF switch {down = 3009, up = 3009, value_down = 1.0, value_up = 0.0, cockpit_device_id = 7, name = _('JTRS On/Off toggle'), category = _('Armament HUD Control Panel')}, -- CICU On & Off for push buttons {down = 3008, cockpit_device_id = 7, value_down = 1.0, name = _('CICU ON'), category = _('Armament HUD Control Panel')}, {down = 3008, cockpit_device_id = 7, value_down = 0.0, name = _('CICU OFF'), category = _('Armament HUD Control Panel')}, -- CICU On/Off for a ON/OFF switch {down = 3008, up = 3008, value_down = 1.0, value_up = 0.0, cockpit_device_id = 7, name = _('CICU On/Off toggle'), category = _('Armament HUD Control Panel')},

In wanted to add GUN PAC ARM / SAFE / GUN ARM to the START/CRANK switch on my Virpil ShaK50 Panel. It is a ON/OFF/ON switch. With the pdf guide of LeCuvier I was able to find the right code for my default.lua. I share it here if someone needs it: {down = 3002, up = 3002, value_down = 0.2, value_up = 0.1, cockpit_device_id = 7, name = _('Gun PacArm/Safe'), category = _('Armament HUD Control Panel')}, {down = 3002, up = 3002, value_down = 0.0, value_up = 0.1, cockpit_device_id = 7, name = _('Gun Arm/Safe'), category = _('Armament HUD Control Panel')},

14 months and no fix. I wanted to add it to my new Virpil ShaKa50 Panel HMS/OFF switch. I need to modify lua's. It makes me really sad. Such things are easy to implement. I can't understand it!

I'm trying to add the CICU and JTRS switches of the A-10C AHCP to my Virpil ShaK50 Panel. At the bottom it has two ON/ON Switches. So I would need CICU ON an CICU OFF as separate actions. All I could find is iCommandPlaneAHCPCICUOnOff. For JTRS I've got the same problem. I've already search in this topic, but didn't found anything. Any ideas?

Would like to have a custom path, too. But it has low priority.

Ich verkaufe den alten Zock-PC von meinem Sohn mit folgender Hardware: Mainboard: MSI Z270 Gaming Pro Carbon CPU: Intel i5 7600K 3.8 GHz (die K Version lässt sich übertackten) CPU-Kühler: Be Quiet Pure Rock Slim Speicher: 2x8GB Cosair Vengeance LPX DDR4 3200MHz 16-18-18 (3200 Mhz ist schon flott) Grafikkarte: MSI GeForce GTX1060 GamingX Twin Frozr VI mit 6GB SSD: Samsung EVO 850 500 GB Gehäuse: Corsair schwarz mit weißem Punisher Aufkleber an der Front und leichten Gebrauchsspuren an den Seitenteilen Netzteil: Corsair Vengeance 550M Multi-Format BlueRay ReWriter von LG Mit frisch installiertem Windows 10 Pro Lizenz stammt von einer Win 7 Pro OEM, welche aktiviert aber noch nicht an ein Microsoft-Konto gebunden ist. Windows7-Verpackung + DVD mit Lizenzschlüssel wird übergeben. Nur notwendigste Treiber installiert (Chipsatz, USB3.1 & Nvidia) damit das System nicht schon softwaretechnisch zugemüllt übergeben wird. Preis: 550 € VB Bitte bedenkt bei dem Preis, dass es alles Markenteile sind und kein NoName-Schrott. Abholung wäre mir lieber, Versand geht aber zur Not auch. Keine Garantie oder Rückgabe, da Privatverkauf. Vielleicht ist das was für einen DCS-Anfänger mit schmalem Budget. Der Rechner wird DCS in VR oder 4k aber nicht schaffen. Wer Interesse hat bitte per PN melden.

Sorry, no. Had no time to do it. Maybe in the chrismas holidays.

Hi, I start the mission with an empty weapon load. I open weapon dialog and add weapons to the stations. In the past all changed stations changed color from green to red in the dsms. Now they stay green. Seen in the stable version today. Best regards kal

I've contacted Binary to integrate the keyboard. But it will take some time. The different versions confuses a lot of people.

I would do it and share it in my git, but I dont know how.

Hi, since some weeks we got this error every time we try to change the password by the server WebUI: 2021-10-20 17:19:12.371 ERROR WebGUI: While parsing encryptedRequest: JSON error: parse error: premature EOF {"ct":"gmIedzbvexpbXrKP6eLnSfVc (right here) ------^ If we stop and start the server it is available without password. It happens no matter if we use Chrome on the lokal server (.html file) or "Home > Personal section > Game servers". Any tipps? Best regards, kal

Every setting of the Utility. But you can run both versions parallel. So you don't need to hurry the configuration of the new version. And you can open both versions at the same time to compare and configure the settings.

Nur noch mal als Lebenszeichen. Nicht das jemand denkt das Projekt gibt es nicht mehr. Mit der ersten Gruppe von 4 Schülern habe ich den A-10C Basiskurs, Aufbaukurs 1 und Waffenbasiskurs durch. Nächste Woche fängt die Gruppe den Waffenaufbaukurs an. Eine weitere Gruppe fängt bald mit dem A-10C Basiskurs an. Sobald alle A-10C Kurse ausgearbeitet und einmal gehalten wurde, beginne ich damit die praktischen F/A-18C Kurse zu erstellen. Das wird aber noch etwas dauen. Ist halt alles eine Mordsarbeit. Aber es macht Spaß und es geht in kleinen Schritten vorwärts. Parallel laufen Workshops mit F-14, F/A-18C, Huey, T-45 & Ka50. Workshops gehen nicht so ins Detail wie Kurse, sind dafür aber flexibler. Wer Interesse hat der sollte uns in unserem Discord besuchen. Im Gegenzug musste ich aber die Arbeiten an der Webseite leider erst mal auf Eis legen. Alles parallel geht halt nicht.

Just start the new version. But you have to reconfigure everything, because in one version the file structure of the settings file was changed without an automatic migration.

I had the same problem. But I did't see any way to do the readback. No F10 menu or "press space bar" dialogue was left. I blowed them up, waited because I thought troops or a helicopter will arrive, but then I decided to leave them alone and RTB. Maybe a dialog can be added to make the readback more clear? Or it will be enogh to kill the manpad. But that is only a small detail issue. Anyway, very nice mission. Thank you very much. Keep up the great work!