Jump to content

towsim

Members
  • Posts

    647
  • Joined

  • Last visited

About towsim

  • Birthday 03/29/1949

Personal Information

  • Flight Simulators
    DCS A-10
    ESP
    FSX
  • Location
    Bavaria, Germany
  • Interests
    Total simulatons
  • Occupation
    Flight and ATC sim cosultant
  • Website
    http://www.ariescon.com/

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If you interface DCS from a DLL or even from any external application running on the same computer, the code shown below works very fine. First of all, you need the window handle of the DCS window. This is done once with GetDCSwindowHandle(). The naming "DCS" and "Digital Combat Simulator" is critical because DCS changed the window name and the window class name several times over the years. The handle is used to switch the keyboard focus to the DCS window before any key is sent. In SendKeyToDCS the focus is switched to DCS first with the API function SetForegroundWindow. After that, the key can be sent with the virtual keycode VK_... and the corresponding keyboard scan code. The latter is language dependent because there are different positions for some keys on different keyboard layouts. For the proper function, the key must be sent twice. The first for a key-down and the second for a key-up signal. Between the two signals a wait of 100 ms is inserted (works even with 10 ms). FindWindow, SetForegroundWindow, and keybd_event are windows API functions. KEYEVENTF_KEYUP is a constant defined in WinUser.h. [color="DeepSkyBlue"]HWND [/color]DCSwindow = [color="Magenta"]NULL[/color]; [color="DeepSkyBlue"]BOOL [/color][color="DarkRed"]GetDCSwindowHandle[/color]() { [color="DeepSkyBlue"]BOOL [/color]rval = [color="Magenta"]FALSE[/color]; [color="DeepSkyBlue"]if[/color](DCSwindow = [color="darkred"]FindWindow[/color]("DCS", "Digital Combat Simulator")) rval = [color="magenta"]TRUE[/color]; [color="deepskyblue"]return[/color](rval); } [color="deepskyblue"]void [/color][color="darkred"]SendKeyDownToDCS[/color]([color="deepskyblue"]char [/color]VK_virtualCode, [color="deepskyblue"]BYTE [/color]KeyboardScanCode) { [color="darkred"]keybd_event[/color](VK_virtualCode, KeyboardScanCode, 0, NULL); } [color="deepskyblue"]void [/color][color="darkred"]SendKeyUpToDCS[/color]([color="deepskyblue"]char [/color]VK_virtualCode, [color="deepskyblue"]BYTE [/color]KeyboardScanCode) { [color="darkred"]keybd_event[/color](VK_virtualCode, KeyboardScanCode, KEYEVENTF_KEYUP, NULL); } [color="deepskyblue"]BOOL [/color][color="darkred"]SendKeyToDCS[/color]([color="deepskyblue"]char [/color]VK_virtualCode, [color="deepskyblue"]BYTE [/color]KeyboardScanCode) { [color="deepskyblue"]BOOL [/color]rval = [color="magenta"]FALSE[/color]; [color="deepskyblue"]if[/color](DCSwindow) { [color="darkred"]SetForegroundWindow[/color](DCSwindow); [color="darkred"]SendKeyDownToDCS[/color](VK_virtualCode, KeyboardScanCode); [color="darkred"]Sleep[/color](100); [color="darkred"]SendKeyUpToDCS[/color](VK_virtualCode, KeyboardScanCode); rval = [color="magenta"]TRUE[/color]; } [color="DeepSkyBlue"]return[/color](rval); }
  2. Dear Modders, I need help for the remote control of the pressure setting turn button. What I tried up to now: Export.lua: From devices.lua (included via ‘dofile’) I found the AAU-52/A as index 26 Altimeter = GetDevice(26) From my DLL (included via: warrior = require(‘spinWarrior’) I get the step value to the variable ‘val’, which works reliable. val = warrior.AltimeterSetting() val can be a positive or negative step value, depending on the turn direction. In command_defs.lua I found the only AAU-52/A command as 3000. Therefore, I make the next call in export.lua, text line 51: Altimeter:performClickableAction(3000,val) At this point, LUA detected an error in the call. I inspected the DCS log file and found the entry Export.lua"]:51: attempt to index upvalue 'Altimeter' (a number value) In another project with the A10, this procedure sequence worked very well. Does anybody know, how to get this turn button under control?
  3. towsim

    April Fools!

    Here, what I experienced. Gear setting becomes unreliable and flaps do not work...
  4. towsim

    April Fools!

    Landin Gear Animation Dear ED, please review the landing gear animation in the left MFD. It is not funny when the gear and the flaps do not react in the normal way. Probably a virus in your team?
  5. want to buy... Hi rel4y, sent you an e-mail to mtwsims@tutamail.com 7 days ago an did not get an answer. Are you still in business? Regards, TOWSIM
  6. Unfortunately not...
  7. Today I ran into the following trap: I noticed, that the mouse cursor is not longer synchronized with the screen resolution. To reach a specific button I had to click a position right of the shown button. The first idea was, that the selected screen resolution in the options menu does not match the physical screen resolution. So, I started to play with the different resolutions. Now the trap. By surprise, I configured a screen setup, where all the important buttons are positioned right outside the displayed DCS screen. The most important button, the ‘OK’ button in the options menu, is not longer available. With other words, I cannot store the selected values nor revert the last made changes. Even the normal way to end the program is not possible. The entire program is not usable anymore. What I tried out so far: I searched for a specific LUA file which contains the faulty resolution. No success… I renamed the ‘Config’ folder in saved Games to force the use of the default ‘Config’ folder with the old, default values. No success… I renamed the ‘MonitorSetup‘ folder and started a ‘Repair’. I got a new ‘MonitorSetup‘ folder but the error remained. My question is, is there any black magic available to set the resolution and aspect of the DCS opening screen? Thanks in advance, BOSSHOG
  8. I experienced a strange error with the latest version of Open Alpha 2.n: Aircraft: Mirage 2000 Airport: Nellis ramp start Mode: VR on with Oculus Rift As soon as I move my head down to look at switches on the consoles, DCS crashes. This bug is permanent and can be recreated every time. Below the relevant lines of the log file: 00105.043 DEBUG SOUNDER: dofile("GroundUnits/Engines/Tanks/AGT1500.lua") 00105.043 DEBUG SOUNDER: dofile("GroundUnits/Engines/Engine.lua") 00105.043 DEBUG SOUNDER: dofile("GroundUnits/Engines/Turbine.lua") 00105.043 DEBUG SOUNDER: dofile("GroundUnits/Engines/Environment.lua") 00105.043 DEBUG SOUNDER: created host MAIN_16777728/main, id=12 00105.043 DEBUG SOUNDER: created sounder MAIN_16777728 as 6 00105.065 ERROR wInfo: negative weight of payload "{Matra155RocketPod}" 00105.070 ERROR VFS: Can't open file //models/m-2000c.edm.json. 00105.360 ERROR_ONCE DX11BACKEND: Can't load 'Fonts/font_general_RU.dds' in texture array ''. 00105.879 ERROR Lua::Config: load error C:\Users\mike\Saved Games\DCS.openalpha\KNEEBOARD/001-missionbriefing-001.lua:can't open 'C:\Users\mike\Saved Games\DCS.openalpha\Data\KneeboardData\missiondata.lua'. 00105.883 ERROR Lua::Config: load error C:\Users\mike\Saved Games\DCS.openalpha\KNEEBOARD/001-missionradios-001.lua:can't open 'C:\Users\mike\Saved Games\DCS.openalpha\Data\KneeboardData\drawingdefinitions.lua'. 00105.903 ERROR Lua::Config: load error C:\Users\mike\Saved Games\DCS.openalpha\KNEEBOARD/002-nevada-navbeacons-001.lua:can't open 'C:\Users\mike\Saved Games\DCS.openalpha\Data\KneeboardData\drawingdefinitions.lua'. 00106.039 ERROR COCKPITBASE: indicators_keeper::link_all: unable to find link source 'FM_proxy' for indicator 12 00111.712 ERROR SOUND: source_add(host:COCKPIT_2D, proto:MagicSeek, alt_proto:): can't find proto 00111.848 DEBUG LuaGUI: ------- onSimulationStart------ true false false 00111.907 INFO EDTERRAINGRAPHICS41: ITerrainGraphicsImpl4::forceLoading(): pos=(-399476, 563.767, -18139.4), radius=100000 00111.980 INFO EDTERRAINGRAPHICS41: ClipmapGraphics::init("splatmap") 00112.323 ERROR_ONCE DX11BACKEND: texture 'noises/noise5.png' not found 00112.684 ERROR_ONCE DX11BACKEND: texture 'noise4.png' not found 00113.364 ERROR EDTERRAINGRAPHICS41: bazar/shaders/metashaders/terrain/5.0/surface5.0.fx|CLIPMAP_NORMAL_MAP|CLIPMAP_SHADOW_MAP|COLORCLIPMAP_ALPHA_IS_AO|COLOR_CLIPMAP|LAKE_COLORCLIPMAP|NODEFINITIONS|NOISE_OP=PhotoshopOverlay|PBR_TEXTURES|SPLATMAP|SURFACE5|TAD_CLIPMAP: no subgeometry current 00116.603 ERROR SOUND: can't load wave: "effects\weapons\gsh301endin" 00117.447 ERROR EDTERRAINGRAPHICS41: bazar/shaders/metashaders/terrain/runway4.1.fx|CLIPMAP_NORMAL_MAP|CLIPMAP_SHADOW_MAP|COLORCLIPMAP_ALPHA_IS_AO|COLOR_CLIPMAP|LAKE_COLORCLIPMAP|NOISE_OP=PhotoshopOverlay|PBR_TEXTURES|RUNWAY_ONLAY|SPLATMAP|SURFACE5|TAD_CLIPMAP: geometry->getStructured(auto: P, N, fabricUV, fabricTextureIndex, decalUV, decalTextureIndex, cracksMaskUV, cracksMaskTextureIndex, dirtMaskUV, dirtMaskTextureIndex, overlayUV, fabricNormalUV, fabricNormalTextureIndex, cracksMaskNormalUV, cracksMaskNormalTextureIndex, fabricNormalTangent, fabricNormalBinormal, cracksMaskNormalTangent, cracksMaskNormalBinormal, specularUV, specularTextureIndex) failed 00120.122 DEBUG LuaGUI: ----onSimulationResume--- 00120.214 WARNING DXGUI: Invalid blur type! 00122.184 INFO EDCORE: try to write dump information 00122.187 INFO EDCORE: # -------------- 20170730-132417 -------------- 00122.189 INFO EDCORE: C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\dxgui_edge_render.dll 00122.191 INFO EDCORE: # C0000005 ACCESS_VIOLATION at EF4E67A3 00:00000000 00122.343 INFO EDCORE: Minidump created. 00122.347 INFO EDCORE: try to write track file
  9. https://forums.eagle.ru/showthread.php?p=3189705#post3189705
  10. https://forums.eagle.ru/showthread.php?p=3189705#post3189705
  11. For those, who have troubles with the HUD visibility against a white background, even seen in VR. I think, I found a solution for the HUD visibility, as long as DCS does not solve the bug: Instead of changing the color values, we have to suppress the alpha functionality. For the A10C: • Open the file C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\Mods\aircraft\A-10C\Cockpit\Scripts\HUD\Indicator\HUD_definitions.lua. • Set all definitions containing ‘additive_alpha’ to ‘false’ For the M2000: • Open and edit the following files C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\Mods\aircraft\M-2000C\Cockpit\VTH\ HUD_definitions.lua. C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\Mods\aircraft\M-2000C\Cockpit\VTH\ HUD_base_appr.lua. C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\Mods\aircraft\M-2000C\Cockpit\VTH\ HUD_page_base.lua. • In the files, set all definitions containing 'additive_alpha’ to ‘false’ After that, you will see the HUD as it was before the update. Before you make the changes, create a save copy of the mentioned files. It is even expected, that the modified files will be overwritten with the next DCS update. It even helps to set the Gamma slider to a lower value to avoid the extreme misty air condition which causes the white background along the horizon.
  12. Hi guys, I am sorry for answering that late. I am bound to the Weekends for private activities. If you you have troubles with the current version, please have a look to the following directories: C:\Program Files\AriesWings\PRCL\ApplicationData And to the Directory, where you started the Installer. Both directories contain a HTML log file. If cannot find a logical reason in the reports, you may mail the log files to support@ariescon.com. I will have a look to it. Sorry…
  13. So, what I found out so far: With the latest version, TeamSpeak changed the entire directory structure for plugins, which is not compatible any longer with Aries Radio. Even the API internals have changed. Since the TeamSpeak API manual is as thick as the cookbook for hot water, it would take too much time for the moment to convert the software to the latest version. Sorry…
  14. Sorry, I did not check the latest TeamSpeack versions since Post 1308. Nevertheless, I will have a look to it. I will post the result here…
×
×
  • Create New...