Jump to content

BATCARLO

Members
  • Posts

    35
  • Joined

  • Last visited

Everything posted by BATCARLO

  1. When in the mission editor I set a DES TOS for an F-16C flight, this is not reported correctly on the cruise page. The first time you enter as single player the DES TOS is correct, but if you change slot it becomes incorrect, and increases over time. In multiplayer, however, it is always wrong and increases over time. The DES TOS instead must always remain the one set in the mission editor. watch the video
  2. Hi, when I set elevation wp from 150 ft to 161 ft, I get 1 foot less. That is if I set ft 152, I get ft 151; with ft 157, I get ft 156 and so on. Please check this video: FA18C WRONG ALTITUDE.mp4
  3. I have tried again successfully. It is necessary to obscure any reflection sources as any additional screens. (where I had extracted the DDI of the F / A-18C). You can do this test, get up from the chair, to move away from the reflection sorces, and re-center the VR view. Another test you can do is to move away from the desk or turn around 90 or 180 degrees, to move away from the reflection sorces, and re-center the VR view.
  4. Take a look: https://www.dropbox.com/s/i9hxfk7p887hqcq/SA5B55 180 degrees turn-00.mkv?dl=0 and another track https://www.dropbox.com/s/twnv4visuzfawtp/SA5B55 180 degrees turn-01.mkv?dl=0 We play with "map only", so we can't track DCS reply...
  5. I am attaching a screenshot from TacView, where you can see the impossible 180 ° turns of the SA5B55, also made without loss of speed ...
  6. Yes, now it's running, but it's not usefull for me...
  7. for me is the same
  8. In GMT radar, also in SEA radar, do not designate moving target with TDC DEPRESS, but designate with Sensor Control Switch in the direction of the DDI with GMT (or SEA) radar. The radar sensor designate keeps moving target, you see his direction and speed... The maverick sensors, when ungaged, points the right target. Sorry my bad English.
  9. Markpoints cannot be designated. Sorry now its working...
  10. Undesignate also deletes too assignments. See the video https://www.dropbox.com/s/sf0dlp5rra57vde/BUG UNDESIGNATE.mp4?dl=0
  11. Run as administrator... new release beta https://github.com/Santi871/DCSWaypointEditor/releases/tag/v1.0.0b1
  12. OpenBeta last release on 05/27/2021. I have assigned 4 different TOOs to my Jdams. When I clicked on undesignate before launching them, it deleted all assigned TOOs.
  13. You can see a short 30 sec. video with the bug here: https://www.dropbox.com/s/ksqdgsqgte3qjmc/PROVA.mp4?dl=0 The designation does not happen on the selected wp, but on the position where the TPOD sensor is even if there was no target designation. Also when the designation is removed, the TPOD sensor moves further close to the aircraft. Same thing if you try to designate the points marked with markpoint, the designation moves to the sensor position of the TPOD.
  14. In DCS / Options / Controls / your favourite aircraft, on the botton left there is Modifier/Switch. You can add a Modifier on the left side, and set it to a joystick button (pinkie paddle on the joystick for me); so it acts as a "shift", when it is hold pressed, all other bottons do other commands than the normal without it. Instead if you want make more profiles, like one for A/A, one for A/G, one for NAV, you need add one or more switch on the right side. They acts as CapsLock, when it is activated, it changes all the assigned commands ar the buttons. I use CapsLock and BlockScorr because they have 2 states: pressed and not pressed. You can use other switch on the base of throttle of the warthog, the have 2 states. Sorry for my english... Inviato dal mio SM-A530F utilizzando Tapatalk
  15. I write you a message Inviato dal mio SM-A530F utilizzando Tapatalk
  16. Dalla lista HTML dei comandi del profilo alla rappresentazione grafica! Nuova versione, ora estrae anche dalla Keyboard. Il programma estrae i comandi DCS impostati sui profili di Thrustmaster Hotas Warthog Joystick e Throttle, rappresentandoli in grafica pronti per essere stampati. Estrae anche da tastiera o dai file *.diff.lua Richiede Microsoft Excel. https://www.digitalcombatsimulator.com/en/files/3308381/
  17. From HTML list of profile commands to graphics! NEW VERSION: now it extracts also from Keyboard From HTML list of profile commands to graphics! From Thrustmaster Hotas Warthog or Keyboard. It requires Microsoft Excel. https://www.digitalcombatsimulator.com/en/files/3308381/
  18. RustBelt, I'm working on it, stay tuned!
  19. Only for Thrustmaster Hotas Warthog. It requires Microsoft Excel. The program extracts the DCS commands set on profiles of the Thrustmaster Hotas Warthog Joystick and Throttle, representing them in pictures. https://www.digitalcombatsimulator.com/it/files/3308381/
  20. Ho condiviso su DSC file utenti un mio programmino per estrarre i comandi assegnati al Thrustmaster Hotas Warthog ottenendoli in formato grafico. Occorre avere Excel. https://www.digitalcombatsimulator.com/it/files/3308381/
  21. Now I have solved with: Each pilot's description.lua file contains: livery = { {"f18c1", 0 ,"F18C_1_DIFF_nickname#1",false}; {"f18c1", ROUGHNESS_METALLIC ,"F18C_1_DIF_RoughMet",true}; {"f18c2", 0 ,"../PVI MARINA dark/F18C_1_DIFF_PROTO2",false}; {"f18c2", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"f18c_glass", 0, "f18c_glass", true}; {"f18c_glass", 2, "f18c_glass_roughmet", true}; {"f18c_glass", 5, "f18c_glass_damage", true}; ... {"F18C_BORT_NUMBER_NOSE_L_100", 0 ,"F18C_1_DIFF_nickname#1",false}; {"F18C_BORT_NUMBER_NOSE_L_100", ROUGHNESS_METALLIC ,"F18C_1_DIF_RoughMet",true}; {"F18C_BORT_NUMBER_NOSE_L_100", DECAL ,"AGS_WF_bort_number_LEFT",true}; ... {"F18C_BORT_NUMBER_KIL_Switz_R_01", 0 ,"../PVI MARINA dark/F18C_1_DIFF_PROTO2",false}; {"F18C_BORT_NUMBER_KIL_Switz_R_01", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"F18C_BORT_NUMBER_KIL_Switz_R_01", DECAL ,"empty",true}; ... {"FPU_8A", 0 ,"FPU_8A_AGS_WF",true}; {"FPU_8A", 2 ,"FPU_8A_Diff_RoughMet",true}; --Pilot {"pilot_F18_helmet", 0 ,"PVI_Hornet_Helmet_nickname#1",false}; {"pilot_F18", 0 ,"../PVI MARINA dark/pilot_F18_marina",false}; {"pilot_F18_patch", 0 ,"../PVI MARINA dark/pilot_F18_patch_marina",false}; } name = "_PVI_Marina_nickname#1" countries = {"USA","ITA"} Where "../PVI MARINA dark/" is the main skin folder.
  22. Hi joey45, I don't quite understand how to use the TRUE parameter. I have a skin "PVI MARINA dark", where for each pilot I would like to differentiate the helmet and nickname. In the main skin there are all the dds files: AGS_WF_bort_number_LEFT.dds AGS_WF_bort_number_RIGHT.dds AGS_WF_bort_number_wing.dds empty.dds F18C_1_DIFF_PROTO.dds F18C_1_DIFF_PROTO2.dds F18C_glass.dds F18C_glass_color.dds FPU_8A_AGS_WF.dds pilot_F18_marina.dds pilot_F18_patch_marina.dds PVI_Hornet_Helmet.dds description.lua While in the individual skins I would like to have only the files: -Skin for pilot #2 i.e. PVI MARINA nickname#1: PVI_Hornet_Helmet_nickname#1.dds F18C_1_DIFF_nickname#1.dds description.lua -Skin for pilot #2 i.e. PVI MARINA nickname#2: PVI_Hornet_Helmet_nickname#2.dds F18C_1_DIFF_nickname#2.dds description.lua etc. Each pilot's description.lua file contains: livery = { {"f18c1", 0 ,"F18C_1_DIFF_nickname#1",false}; {"f18c1", ROUGHNESS_METALLIC ,"F18C_1_DIF_RoughMet",true}; {"f18c2", 0 ,"F18C_1_DIFF_PROTO2",false}; {"f18c2", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"f18c_glass", 0, "f18c_glass", true}; {"f18c_glass", 2, "f18c_glass_roughmet", true}; {"f18c_glass", 5, "f18c_glass_damage", true}; ... {"F18C_BORT_NUMBER_NOSE_L_100", 0 ,"F18C_1_DIFF_nickname#1",false}; {"F18C_BORT_NUMBER_NOSE_L_100", ROUGHNESS_METALLIC ,"F18C_1_DIF_RoughMet",true}; {"F18C_BORT_NUMBER_NOSE_L_100", DECAL ,"AGS_WF_bort_number_LEFT",true}; ... {"F18C_BORT_NUMBER_KIL_Switz_R_01", 0 ,"F18C_1_DIFF_PROTO2",true}; {"F18C_BORT_NUMBER_KIL_Switz_R_01", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"F18C_BORT_NUMBER_KIL_Switz_R_01", DECAL ,"empty",true}; ... {"FPU_8A", 0 ,"FPU_8A_AGS_WF",true}; {"FPU_8A", 2 ,"FPU_8A_Diff_RoughMet",true}; --Pilot {"pilot_F18_helmet", 0 ,"PVI_Hornet_Helmet_nickname#1",false}; {"pilot_F18", 0 ,"pilot_F18_marina",true}; {"pilot_F18_patch", 0 ,"pilot_F18_patch_marina",true}; } name = "_PVI_Marina_nickname#1" countries = {"USA","ITA"} I understand that with the TRUE parameter I can use a livery zip folder where there are all the dds files of the main skin. But I don't understand how to call this zip file, in which folder to put it and how to recall it. Thanks bye.
  23. Translation guides in italian Hi Charly, many thanks for your wonderful guides. I would like to translate the Hornet into Italian and I would like to ask you for permission. I read another similar request on the forum, but without an answer. Thanks again Hello Carlo
  24. OSB text with black background boxes in the AMPCD ? Hi, there is a way to get OSB text with black background boxes in the AMPCD, like in A10 ? They are uglier but more readable when overlaid on the map! Or can they be set in other colors? thank you
  25. I do not know. I believe they are not exports from the F18 but from A10 !
×
×
  • Create New...