Crash_Horror

Day 2: The fight is raging on! Yesterday in a mad dash REDFORCE captured Sochi and Sochi/Maykop FARP while BLUFORCE grabbed Tbilisi/Beslan FARP. Today we anticipate a great comeback from BLUFORCE, so strap in and prepare to defend your assets!

I know it is just a test run but: They took Gudauta! Alert! nnnnNNNNNNNOOOOOOOoooooo!

Release the Kraken!

F/A-10C dogfights! I made a video with air to air engagements from the last 4 sessions of the campaign. We mostly scream in greek, but you can get the gist. Enjoy!

'Not because it is easy, but because it is hard'. :D

:D The complexity and fluidity you get when you fly with 40+ people absolutely kicks your butt. I flew the A-10 throughout the two campaigns. Trying to navigate, manage systems, weapons, targeting, coordinate with wingmen, maintain some semblance to situational awareness, while on average five people constantly scream at you at the same time as you try to dodge that evil F-15 that won't stop beeping at you, is just ridiculous! Not to mention the typing of coordinates, TGP slew fiddle amongst non stop missile warnings and fox/rifle calls. And then the Ground commander mistakes you as a fighter and sends you to take out that F-15 again, that is getting close and mean, oh and just go through the other two enemy A-10s on your way there. And you have to do it right? Not that you will succeed. You can't complain though can you! Like having a B role in an 80's horror film that seems to have no end. Seriously though, awesome fun. Can't wait for the next one!

Confirming, I am still available.

I am sorry for this but... I could not... resist...

I had the same stutters after a hdd change / fresh install. I had gone through everything I could think of for about a week, then the windows service pack came up in the windows update. Quite late on the update queue... After that, the stuttering stopped. I can't be sure that the SP was what fixed it though.

Kindly consider me for any waitlist. I will fly anything for food. 373vFS_Crash

Fixed! Indentation error: https://github.com/crash-horror/dcs-mission-statistics-xcom/commit/0d96aab0c162bc4a6e71843b7fb4b19d48e8dcc0 Binary: https://github.com/crash-horror/dcs-mission-statistics-xcom/releases/download/v0.16/get-mission-stats-v016.rar :pilotfly:

Thanks xcom, cool stuff. I was fiddling with a python script that does the same but bypasses the database thingy. So after much adventure and a fair amount of copying your work, i came up with this: https://github.com/crash-horror/dcs-mission-statistics-xcom The actual script: https://github.com/crash-horror/dcs-mission-statistics-xcom/blob/master/get-mission-stats.py A binary(exe): https://github.com/crash-horror/dcs-mission-statistics-xcom/releases/download/v0.16/get-mission-stats-v016.rar It parses the CSV file that your other scripts generate and creates a html page. I am a complete amateur so bear with the ugly code :music_whistling: Also it seems to work with all the csv files I managed to get my hands on, except the one from last Sunday's (May 25) Caucasus Blizzard. Did you change sthing on the server? Thanks again, cheers.

OK here it is. A version for the A-10C using the 'mainpanel' thingy: function LuaExportStart() -- Works once just before mission start -- default_output_file = io.open("YOUR_ENGINE_DATA_FILE.log", "w") -- writes a file to DCS root directory -- end -------------------------------------------------------------- MainPanel = GetDevice(0) function LuaExportActivityNextEvent(t) local tNext = t local engine_RPM_left = MainPanel:get_argument_value(78) * 100 local engine_RPM_right = MainPanel:get_argument_value(80) * 100 default_output_file:write(string.format("t = %.2f RPM left = %.2f RPM right = %.2f\n", t, engine_RPM_left, engine_RPM_right)) tNext = tNext + 1.0 -- data collected once every second / change this according to preference return tNext end -------------------------------------------------------------- function LuaExportStop() -- Works once just after mission stop -- default_output_file:close() end And a version that checks if you fly an A-10C or something "else": function LuaExportStart() -- Works once just before mission start -- default_output_file = io.open("YOUR_ENGINE_DATA_FILE.log", "w") -- writes a file to DCS root directory -- end -------------------------------------------------------------- aircraft = LoGetObjectById(LoGetPlayerPlaneId()) MainPanel = GetDevice(0) if (aircraft.Name == "A-10C") then -- checks for either A-10C or 'other' aircraft function LuaExportActivityNextEvent(t) local tNext = t local engine_RPM_left = MainPanel:get_argument_value(78) * 100 local engine_RPM_right = MainPanel:get_argument_value(80) * 100 default_output_file:write(string.format("t = %.2f RPM left = %.2f RPM right = %.2f Aircraft = %s\n", t, engine_RPM_left, engine_RPM_right, aircraft.Name)) tNext = tNext + 1.0 -- data collected once every second / change this according to preference -- return tNext end else function LuaExportActivityNextEvent(t) local tNext = t local engine = LoGetEngineInfo() default_output_file:write(string.format("t = %.2f RPM left = %.2f RPM right = %.2f Aircraft = %s\n",t,engine.RPM.left,engine.RPM.right, aircraft.Name)) tNext = tNext + 1.0 -- data collected once every second / change this according to preference -- return tNext end end -------------------------------------------------------------- function LuaExportStop() -- Works once just after mission stop -- default_output_file:close() end This one also writes the aircraft type at the end of each line. :noexpression: As I understand it, every DCS:level module has its own "mainpanel_init.lua" with its own IDs for different instruments so it propably won't work for others. I may be wrong. But you get the idea, you can search for "mainpanel_init.lua" in the DCS folder and add more aircraft if you need to.

Actually it appears you are partially right Chromium. I tested it with FC3 planes and worked fine, but it appears it won't work with the A-10C. This must be very recent, cause I use something similar and had no problems until now. It must be the last patches? I don't own any helos to test it further, just A-10 & FC3. I am not familiar with "mainpanel", will have to look into it.

Of course it works, I would not have posted it without testing it. :thumbup:

Paste this into your "C:\Users\user\Saved Games\DCS\Scripts\Export.lua" function LuaExportStart() -- Works once just before mission start. -- default_output_file = io.open("YOUR_ENGINE_DATA_FILE.log", "w") -- writes a file to DCS root directory -- end -------------------------------------------------------------- function LuaExportActivityNextEvent(t) local tNext = t local engine = LoGetEngineInfo() default_output_file:write(string.format("t = %.2f RPM left = %f RPM right = %f \n",t,engine.RPM.left,engine.RPM.right)) tNext = tNext + 1.0 -- data collected once every second / change this according to preference -- return tNext end -------------------------------------------------------------- function LuaExportStop() -- Works once just after mission stop -- default_output_file:close() end It creates a "YOUR_ENGINE_DATA_FILE.log" file in the DCS root folder containing data like this: t = 0.00 RPM left = 67.500000 RPM right = 67.500000 t = 1.00 RPM left = 67.500000 RPM right = 67.500000 t = 2.00 RPM left = 67.500000 RPM right = 67.500000 t = 3.00 RPM left = 67.705765 RPM right = 67.705765 t = 4.00 RPM left = 76.481903 RPM right = 76.481903 t = 5.00 RPM left = 92.065933 RPM right = 92.065933 t = 6.00 RPM left = 103.399094 RPM right = 103.399094 t = 7.00 RPM left = 100.496941 RPM right = 100.496941 You can change the formating by modifying this line: default_output_file:write(string.format("t = %.2f RPM left = %f RPM right = %f \n",t,engine.RPM.left,engine.RPM.right)) You can also change how often the values are written. I have set it to 1.0 second tNext = tNext + 1.0 The engine data that can be exported is described by ED here: LoGetEngineInfo() -- (args - 0 ,results = table) engineinfo = { RPM = {left, right},(%) Temperature = { left, right}, (Celcium degrees) HydraulicPressure = {left ,right},kg per square centimeter FuelConsumption = {left ,right},kg per sec fuel_internal -- fuel quantity internal tanks kg fuel_external -- fuel quantity external tanks kg }

Do you have a second monitor and don't know what to do with it? Do you want to clearly visualize the Gs you are puling in a dogfight? Now there is a solution for YOU! * ED changed some stuff, again, so now it works with FC3 aircrafts AND A-10C! DOWNLOAD: For monitors with 1280 vertical resolution or above. For monitors with 1024 or 1080 vertical resolution, a 'compact' version. INSTALATION: Add this code to your C:\Users\~\Saved Games\DCS\Scripts\Export.lua (If the 'Export.lua' or the 'Scripts' folder do not exist, just create them) ------------------------------------------------ ------------START OF GEE-METER CODE------------- ------------------------------------------------ function LuaExportStart() package.path = package.path..";.\\LuaSocket\\?.lua" package.cpath = package.cpath..";.\\LuaSocket\\?.dll" socket = require("socket") host = "localhost" port = 1625 c = socket.try(socket.connect(host, port)) c:setoption("tcp-nodelay",true) end ------------------------------------------------ function LuaExportAfterNextFrame() local Gee = LoGetAccelerationUnits() socket.try(c:send(string.format("%+.2f",Gee.y))) end ------------------------------------------------ function LuaExportStop() c:close() end ------------------------------------------------ --------------END OF GEE-METER CODE------------- ------------------------------------------------ Extract the previously downloaded folder to the path of your liking and run the executable. When you first run it, the windows firewall thingy might pop-up, click "allow access" for your private network. Nothing fishy here, DCS is using a socket to communicate data to it. Have fun! NOTE: If you have "Python 3" installed on your system, you can use the python scripts: Github