Fasu

Hello, Can LoGetWorldObjects("airdromes") provide information about airport frequencies? I know this command can find the coordinates (value.LatLongAlt.Lat and value.LatLongAlt.Long), airport runway numbers (value.Heading), but I don't know how to ask for the frequencies of the airport. If not, where can I find complete documentation on this subject?

Hello, I use this standard function (provided by the official export.lua template): local o = LoGetWorldObjects() for k,v in pairs(o) do default_output_file:write(string.format( "%.0f,%f,%f,%f,%f,%f,%d,%s\n", t, v.LatLongAlt.Lat, v.LatLongAlt.Long, v.LatLongAlt.Alt, v.Heading, magneticVariance, k, v.Name)) end It works fine, but in multiplayer with multiple devices it returns data from all devices. However, I would like to obtain only the data of my aircraft, in my export log file. I don't know how to modify the code for this. Thank you for your help, EDIT In fact, this code seems not to work on some public servers. However, it works if I launch a mission on my DCS in multiplayer. In short, you have understood: what I am looking for is a code that works in all cases (and especially in multiplayer on external servers), and which only returns data from MY aircraft.

Hi everyone, I am trying to extract data from DCS. The following code works perfectly... when I'm on a mission with a single aircraft in "player" mode: function LuaExportActivityNextEvent(t) local tNext = t if default_output_file then local o = LoGetWorldObjects() for k,v in pairs(o) do default_output_file:write(string.format( "%.0f,%f,%f,%f,%f\n", t, v.LatLongAlt.Lat, v.LatLongAlt.Long, v.LatLongAlt.Alt, v.Heading)) end local aircraftPitch, aircraftBank, aircraftYawTrue = LoGetADIPitchBankYaw() aircraftPitch = aircraftPitch * 57.3 aircraftBank = aircraftBank * 57.3 aircraftYawTrue = aircraftYawTrue * 57.3 -- true heading default_output_file:write(string.format("aircraftYawTrue : %.2f\n", aircraftYawTrue)) local aircraftYawMagnetic = LoGetMagneticYaw() aircraftYawMagnetic = aircraftYawMagnetic * 57.3 -- magnetic heading default_output_file:write(string.format("aircraftYawMagnetic : %f\n", aircraftYawMagnetic)) local aircraftHeading = aircraftYawMagnetic -- this cound be negative if aircraftHeading < 0 then aircraftHeading = aircraftHeading + 360 end -- removes the negative local magneticVariance = aircraftYawTrue - aircraftYawMagnetic -- works for all maps default_output_file:write(string.format("%f\n", magneticVariance)) end tNext = tNext + 2.0 return tNext end The result of the log file then is: The problem : On the other hand, when I switch the aircraft to "client mode" (in the mission editor), then this code no longer works. Nomore output after "ProductVersion: 2.7.14.24228". Specifically, the first part alone works, but the second part below no longer works. Thus, the code below (with the second part commented) works, with an aircraft in ""client" mode: function LuaExportActivityNextEvent(t) local tNext = t if default_output_file then local o = LoGetWorldObjects() for k,v in pairs(o) do default_output_file:write(string.format( "%.0f,%f,%f,%f,%f\n", t, v.LatLongAlt.Lat, v.LatLongAlt.Long, v.LatLongAlt.Alt, v.Heading)) end -- local aircraftPitch, aircraftBank, aircraftYawTrue = LoGetADIPitchBankYaw() -- aircraftPitch = aircraftPitch * 57.3 -- aircraftBank = aircraftBank * 57.3 -- aircraftYawTrue = aircraftYawTrue * 57.3 -- true heading -- default_output_file:write(string.format("aircraftYawTrue : %.2f\n", aircraftYawTrue)) -- local aircraftYawMagnetic = LoGetMagneticYaw() -- aircraftYawMagnetic = aircraftYawMagnetic * 57.3 -- magnetic heading -- default_output_file:write(string.format("aircraftYawMagnetic : %f\n", aircraftYawMagnetic)) -- local aircraftHeading = aircraftYawMagnetic -- this cound be negative -- if aircraftHeading < 0 then aircraftHeading = aircraftHeading + 360 end -- removes the negative -- local magneticVariance = aircraftYawTrue - aircraftYawMagnetic -- works for all maps -- default_output_file:write(string.format("%f\n", magneticVariance)) end tNext = tNext + 2.0 return tNext end The result of the log file then is: I spent several hours trying to figure out where the problem could come from. I specify that the problem persists even after having commented all the other lines of the export.lua file (the lines SRS, SIMSHAKER, DCS-ExportScript, ...) A solution ? An idea ? EDIT : OK, finally by multiplying the tests, I understood: I had to launch my mission on a server (and not launch it locally mono-player). When the mission is really on a server, the data export works. (Except perhaps if the mission editor has forbidden it...)

thank you very much for your answer. However, I made an erratum in my question. The problem does not seem to be related to the map, but rather to the player vs client aircraft mode. I keep doing tests to understand.... EDIT : Ultimately, using the (commented) code provided in the export.lua which is in the DCS installation folders, it works, even in multiplayer. Here is the code: function LuaExportActivityNextEvent(t) local tNext = t if default_output_file then local o = LoGetWorldObjects() for k,v in pairs(o) do default_output_file:write(string.format("t = %.2f, ID = %d, name = %s, country = %s(%s), LatLongAlt = (%f, %f, %f), heading = % f\n", t, k, v.Name, v.Country, v.Coalition, v.LatLongAlt.Lat, v.LatLongAlt.Long, v.LatLongAlt.Alt, v.Heading)) end end tNext = tNext + 5.0 return tNext end ...but I'm still interested in an explanation, because when I test other data exports (for example: LoGetADIPitchBankYaw() ), I encounter the same problem: it doesn't work in ''client'' mode. EDIT 2 : OK, finally by multiplying the tests, I understood: I had to launch my mission on a server (and not launch it locally mono-player). When the mission is really on a server, the data export works. (Except perhaps if the mission editor has forbidden it...)

Hello, Thanks for this code: local Thatsme = LoGetSelfData() local Thatsmename = Thatsme.Name -- LatLongAlt = { Lat = , Long = , Alt = } local ThatsmeLat = Thatsme.LatLongAlt.Lat local ThatsmeLong = Thatsme.LatLongAlt.Long local ThatsmeAlt = Thatsme.LatLongAlt.Alt local name = LoGetPilotName() local t = LoGetModelTime() if default_output_file then if Thatsmename then --default_output_file:write(string.format("Time = %.2f, PlayerName = %s, planetype = %s, Lat = %.2f, Long = %.2f, Alt = %.2f,", t, name , Thatsmename, ThatsmeLat, ThatsmeLong, ThatsmeAlt)) --default_output_file:write(string.format("thatsmename = %s, ", Thatsmename)) end end There is something very surprising about me. It works when the aircraft is set in "player" mode (in the mission editor), and it doesn't work when the aircraft is set in ''client'' mode. How is it possible ? An idea ?

Hello, Thank you @hreich for this RESHADE solution, which is quite obscure for me ;-( So I too am interested in a little practical guide

Hello, Thank you for this detailed explanation. I fully understand the choice, it seems logical indeed. I will try to test your proposal to cross ''left-right'' and ''CPG-PLT''. However, in my personal case, I feel like I only need the place of the PLT, never caring about the instruments of the CPG. But probably my need will change when I have a little better understanding of how apache works, GEORGES AI, detection and weapon systems, et cetera. à+ / fasu

Hello Osram, Once again you were right with "In the Helios Control Center there is a retrigger "delay" setting in ms when you open it's addition options." ==> Now everything works perfectly here! I even managed to find how to manipulate the rotator buttons with my finger, without your help ;-)) I then had fun redrawing a Helios interface with enlarged MFDs, moving the other buttons, especially those on the keyboard. It's quite simple, and it allowed me to discover a little more about how the Helios software works. It's quite important for me because my touch screen is small and with low resolution, and it's not very comfortable when MFDs are small. I understand your explanations on the design choices. However, I still have questions: From the moment when DCS imposes to be able to display only one of the MFDs (either those of the PLT, or those of the CPG), and that it is necessary to restart DCS if you want to switch, what is the point of have both possibilities (PLT and CFG) in the Helios profile? Wouldn't it be more relevant to have two separate Helios profiles (2 files: one for the PLT profile + 1 for the CPG profile)? That said, I guess most players choose the PLT instead and then trust the AI George....???? (but I remind you that I am very beginner on the apache) This solution would also perhaps avoid having to edit (comment out certain lines) in the file ....SavedGames\DCS.openbeta\Config\MonitorSetup. What do you think about it ? à+ / fasu

Hello Osram, I'm a little ashamed, but you were right with "Have you tried "dragging" the switches or CPG/PLT switch up/down... with your finger? It's normally not meant to be a touch/click function.". Eventually I tried using my old touchscreen Chromebook. It works, and even much better than with my iPad. My feedback: - SpaceDesk seems more stable, better configurable, than Duet Display. Moreover, it works on old versions of iPad. And besides, it's free. - The connection (wifi) with my ChromeBook (SpaceDesk Android app in the chromebook) is much faster than the connection (wifi also) with the iPad (ipad 3rd gen) always with SpaceDesk: pressing a button displays a result on after 1.5 to 2 seconds for the iPad, while it's almost instantaneous for the Android/ChromeBook. In short, everything works. Except the finger click doesn't always work. Sometimes this seems to be interpreted as a quick double click (As if the MFD button was pressed twice in a row). But not always... It's probably a "finger click delay" setting, but I don't see where to set it yet (maybe in SpaceDesk, maybe in Windows, maybe in my Chromebook... or nowhere in which case it may not be usable on a daily basis). Otherwise, I was wondering. What is the use of having the location of the TEDAC in the Helios space of the PLT, since this space is always empty (black)? I specify that I am a great beginner on the AH-64D! Wouldn't it be better to take advantage of this unused space to enlarge the MFDs for example? Either way, thanks again for everything. Indeed, when I decided to test Helios a few days ago after the release of Apache, I studied some tutorials and it scared me a little. And thanks to the sharing of your .zip with all the files and especially the detailed installation guide, it's child's play! This opens up new perspectives for my DCS cockpit

Hello Osram, Thank you for your detailed feedback on the ED forum. Finally, I installed an old Ipad (3rd gen), connected with SpaceDesk (because Duet Display was not available for my old version of iOS). The screen is smaller, but that should suffice (I may see to enlarging the size of the buttons or rearranging the profile). I'll see if a faster connection is possible with a cable rather than Wifi, but I don't think it's possible with this old iPad that doesn't have Lightning. Note that I also upgraded to version 0.4 (by the way, thank you for the explanations to go from 0.3 to 0.4!) and I also did yesterday's DCS update (by the way, thank you for the explanations !). In fact, really thank you very much for the explanations: it's rather rare that creators take the time to explain step by step for neophytes. Many thanks for that. So : - The TEDAC is only displayed when I sit down at the CPG (key 2 on the keyboard). - The TouchScreen works but only on the TEDAC buttons - I have commented out the lines AH64_LEFT_CPG_MFD and AH64_RIGHT_CPG_MFD. And the two MFDs of the PLT are displayed correctly, regardless of my position in the helicopter. But the MFD buttons do not react. - In my Helios, the left bar indicates CPG (and not PLT). The switch which seems to allow to switch between CPG and PLT does not work (it is not clickable, neither with the mouse, nor with the finger). - I think I managed to accomplish step 1.8 (even if I don't understand everything technically), I haven't "re-configured" and I have "preflight Yellow". I think my problem is therefore a story of switching between PLT and CPG, but I don't see how to solve it. Edit: I did the following test - I swapped CPG and PLT in H_AH64D_Multiseat_SwitchPit.lua (reversing the two commented lines) - It is therefore the MFDs of the CPG that are displayed correctly: and, this time, the buttons are clickable. - Finally, I therefore think that my problem is the small switch of the profile which, I suppose, allows to change the buttons between Thank you for your proposal for a "co-op session"; I'm not against it, on the contrary (it will allow me to thank you in person), but I speak English very very badly, I don't think we will be able to understand each other orally ;-(.

Hello, Thank you very much for this version 0.3. I was able to install (very easily with your installation guide) and... it works !! Helios appears on my second screen. Only problem : the buttons are not clickable (neither with the mouse nor with the finger - it's a touch screen). Note that my second screen is an old ChromeBook, connected with Duet-Display (chromebooks can launch android apps). I also specify that the 'click' works normally elsewhere. Weird, I'll try to search, but I'm afraid that my problem is not related to Helios, nor to your profile. à+ / fasu Ps: An idea for the installation guide: for newbies like me, explain that you have to remember to adjust the graphic parameters in DCS World.

Hello Osram, I will try to install soon. But, from now on, many thanks for sharing and many many thanks for the effort to have produced a detailed installation manual !

Hello, Here is how I adapted the MK.IV for helicopter use (the objective was not to have force feedback towards the center). Simply removing the spring works poorly, as the weight of the pedals causes the pedals to swing to one side if foot pressure is released). With a rubber band (2 rubber bands in my case), the force of the rubber band exactly compensates for the weight of the pedals. So : - The crank remains in its position when you lift your feet. - There is no return to the central position. @ Sokol1_br: thank you for your answer. Even after disassembling the MK.IV I still can't see where this part could attach ... weird.

Hello everyone, I have received my VKB rudder MK.IV. In the box, there is a plastic part (with two small screws that seem to fix this part somewhere), but I don't know what it can be used for. Attached photo. There is no user manual, and I don't find any documentation on the internet on this subject. Any idea ?