Nero.ger

if you Click "DATA" (lower right) two times, does it disappear? first click should open the page you actualy see and second click closes it again (if it works as intend)

with a big enough 'crowbar' you could probably mod the L39 into anything that requires a two seater system :music_whistling: (but i agree on the C101 and the hawk with you) and yea, Bronco is a 'stfu and take my money' :)

soweit ich mich errinern kann sind die Ausgänge des Arduino bis maximal 40mA belastbar, schau also vorher in das Datenblatt des Servos bevor du nen MasterCaution und bischen rauch hast ;)

io,lfs and os functions are blocked in mission scripts to prevent missions stealing your credit card or wreking your harddrive :) there is a way to deactivate those protections (see '\Scripts\MissionScripting.lua') but its on a 'per person basis' so even if you do it everyone who wants to play your mission has to do it himself

have you tried the "apply gamma correction" option? (at least that what its called in GIMP)

this is indeed a strange bug, does it appear directly after start? or did you do something bevor on the MFD? 1) LaserTemp is only available in the HUD as far as i know and i saw no connection between laser Temp and usage/failures. so i did not implement it in the HUD. 2) Buttons... one of my "holy grails"..... to add clickable buttons one would need to edit the Cockpit-EDM-File, which is not possible or not 'legal' so far i found no work around :(

EDM files are 3d-objects DDS files are 'bitmaps' so...what exactly are you trying to do? :)

THAT explains A LOT :doh:

i am "carefuly" sure that at least the a10c's map can be modded in. The abris on the other hand is an entirely different beast...

well i guess its hard to find someone who can answer your question with a high degree of accuracy (beeing either an actual coaxial pilot or aircraft engeneer) since i am neither one or the other, rate my comment with an accuracy of an early AIM7 ;) So the flightmodel: It feels real and convincing is all i can say and if you switch of all Assists it becomes a real handfull. Regarding YT-Vids, the Ka50 has an...interresting Autopilot/Trim System which makes it a stable platform so you can concentrate on other things (remember its a solo machine in a time where the cobra/apache has 2 people). And that will get you into your sniping spot and home. But the challange comes from handling the Assists when things go south and you need to perform some extrem manouvers without the to blades kissing each other. As for the combat, if i would be a real pilot i would want a boring mission because i dont want to die. So its about prePlaning and approach , if the enemy shoots at you theres something gone wrong in the planning room. even in a fast and competitive MP enviroment, you (should) know on take off where your sniping spot will be. as allways my last comment. If you want seat of your pants action, the ka50 might not be your bird but it you are the "sniper"-type of player whos fun comes from crawling 30min throu the mud to get the perfect kill, the Ka50 might be for you. and if you realy mastered everything, start hunting fighterJets... ;)

my notes in front of me have by 'pure coincidence' written "Ground mapping radar" on them ;)

depends on where you come from, you can see them on the F10 map in the upper left corner (need to change coord system with ctrl-z or y) you can get them from the MIZ file where they are called x and y(z) in LUAdevices you can call, for example local tmp_mission_route = get_mission_route() local tmp_lat local tmp_long for i = 2, #tmp_mission_route do WPT_data[i-1].m_x = tmp_mission_route[i]["x"] WPT_data[i-1].m_y = tmp_mission_route[i]["y"] WPT_data[i-1].alt = tmp_mission_route[i]["alt"] tmp_lat,tmp_long = Terrain.convertMetersToLatLon(WPT_data[i-1].m_x,WPT_data[i-1].m_y) WPT_data[i-1].lat_x = tmp_lat WPT_data[i-1].long_y = tmp_long end you can call Data_Raw = get_base_data() local self_loc_x , own_alt, self_loc_y = Data_Raw.getSelfCoordinates() to get your own coordinates (again in meters, thankfully!) while we are at it ground_alt = math.ceil(Terrain.GetHeight(x, y)) gives you the hight of a point on the terrain. why the Ceil function? because if you want to check Line of Sight to a point its better if its 90cm above the ground than exactly on the ground which is done by Terrain.isVisible(x1, alt1, y1, x2, alt2, y2), in case you are wondering :-D i think that should cover it :smartass:

just realized it was the wrong function, it should be :) {latitude,longitude} = LoLoCoordinatesToGeoCoordinates(x,z);

while i never tested this in the export.lua, but the there is no need because {x,y,z} = LoGeoCoordinatesToLoCoordinates(longitude_degrees,latitude_degrees) can be called in the export.lua (if it works, never used it myself)

if i am not totaly wrong, you can see the Route of the Aircraft you are in in the Kneeboard? edit: in case someone in the future stubles across this thread in search for a lua function to convert :) Terrain = require('terrain') lat,long = Terrain.convertMetersToLatLon(meter_x,meter_z)

i would suspect the reason is that you are looking very slightly downwards. so if you look upwards and move you head down a bit (not tilting, just up/down movement) they probably line up (all guesswork here, i am poor and only have one screen ;) )

there is a function('LoGetRoute()') in the export.lua to grad nav points but it was bugged last time i checked, but i suspect by 'export' you mean the reading the .miz file :) i know of no easy calculation outside of using lua and DCS-Functions to convert Coordinates.

the question is, what is your intention? and in what enviroment? Export.lua? LuaDevice?

thank god i brought the F5 in the easter sale!

have you considert your altitude? unless both you and your target are on the same altitude the distantance will not be correct. Since the laser is measuring throu 3d-space while coords are one a 2d plane. Pythagoras might help you here ;)

if its the one from the Transport script it just lases targets without the need for coms, which is actualy a good thing because the original Jtag is somewhat tempramental and not every aircraft can use the Frequency(f5e comes to mind)

+1 because in on "open" MP server i am to scared to allow someone in the back...

christmas seems to come early this year :-D

seems the snapView issue is back in

\DCS World\Mods\aircraft\A-10C\Cockpit\IndicationTextures all texture files for the Cockpit \DCS World\Mods\aircraft\A-10C\Cockpit\Scripts\materials.lua materials["HUD_IND_GREEN"] = {0, 255, 0, 255} {R,G,B,Opacity}