Jump to content


  • Posts

  • Joined

  • Last visited

About Leadnap

  • Birthday October 12

Personal Information

  • Location
    Colorado, USA
  • Occupation
    IT by day, fighter pilot by night

Recent Profile Visitors

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

  1. Not game breaking - but the JHMCS sensor is missing in the external 3d model.
  2. I am working on a complete tutorial series to replace my earlier ones for release later this year.
  3. I've rebound it dozens of ways and nothing did the trick. However - ED support helped out and here is what worked: 1) Rename the C:\Users\----\Saved Games\DCS.openbeta folder to Temp 2) Run the Repair utility 3) Relaunch DCS Good idea though is to save your configs and bindings - you're going back to vanilla. I ran the repair tool multiple times and it didn't do anything but renaming the folder then doing so fixed the issue.
  4. @Oilman100 I completely uninstalled VA today (even though it wasn't connected to DCS anymore) and still no joy.
  5. I have Voice Attack but not for DCS (was going to set that up next actually...). I wonder if there are hooks though? Might go digging around now looking for that.
  6. I've searched around on the forums and seen various reports of this but after the most recent open-beta update my comms menu will not load. I've mapped it to various keys (on multiple devices), nothing. When I open the binding menu pressing the key goes right to the binding but no matter what in every module I cannot use "\" (or any other binding) to bring the comms menu up. Easy communication is off (toggled that too). Completely removed everything but the vanilla OB game (or cleared out best I can tell). Also have noticed that missions are launching in pause and the briefing does not load. May or may not be related but that is the only other thing I've noticed out of place. dcs.log
  7. For those dealing with this annoying AV issue, once you tell the AV to ignore the DCS folder, make sure to do a full repair on DCS with the tool.
  8. Ugh - think if I place them in the CoreMod Livery folder for the AJS-37 they'll work. Should make progress this week if that is so!
  9. I would certainly love to see those dimensions for a build! Eagerly tuned.
  10. I've completely removed all AJS-37 livery files from the /savegame and install paths and the ModelViewer2 application still see's files that don't exist in the mapped directory - despite their being empty. When I save new .DDS files into the correct AJS-37 livery folder ModelViewer doesn't see them either. Can't progress getting this one done until I can see the work in MV again.
  11. @Lee Are you having issues with ModelViewer not seeing the folders? I have emptied all the Viggen folders of any livery and yet Model Viewer keeps showing me ones that don't exist.
  12. It wasn't so much that I flaked, but lost the original project files in a corruption that cost me all my AJS-37 works, and limited time to go back and complete the project. I have two paid F-16 skins to finish and I am back to doing free livery work, this project is at the top of that list. I'm 30% done with the main fuselage. It isn't that it is hard to do - but time consuming making lines connect correctly between parts - something a lot of people ignore. Just because I am doing it and it is taking a long time doesn't mean others can't jump in and do it either. This isn't paying my mortgage.
  13. Do you mind if I borrow your darker feathers for some projects?
  14. Thanks so much for explaining this! For those who are not LUA masters (like myself) here is what the total Description LUA should look like as an example for the default names with this code: livery = { {"F16_bl50_Main_1", 0, "f16_bl50_main_1", false}; {"F16_bl50_Main_1", ROUGHNESS_METALLIC, "F16_bl50_Main_1_RoughMet", false}; {"F16_bl50_Main_2", 0, "f16_bl50_main_2", false}; {"F16_bl50_Main_3", 0, "f16_bl50_main_3", false}; {"F16_bl50_Kil", 0, "f16_bl50_kil", false}; {"F16_bl50_Kil", ROUGHNESS_METALLIC, "f16_bl50_kil_roughmet", false}; {"F16_bl50_wing_L", DIFFUSE, "f16_bl50_wing_l", false}; {"F16_bl50_wing_R", DIFFUSE, "f16_bl50_wing_r", false}; {"pilot_F16_patch", 0, "pilot_f16_patch", false}; } custom_args = { [1000] = 1.0, -- change of type of board number (0.0 -default USA, 0.1, 0.2, 0.3, 1.0 not drawn) [1001] = 1.0, -- vis refuel board number (0.0 drawn, 1.0 not drawn) [1002] = 1.0, -- change of type intake board number (0.0 two digits, 0.1 three digits, 1.0 not drawn) [1003] = 1.0, -- vis nouse board number (0.0 drawn, 1.0 not drawn) } name = "NAME" countries = {"USA",} ((You could in theory take out the --text but I left it so it was clear where this went. Feel free to correct the hell out of that as I am not a LUA editor but making this adjustment made it work!))
  • Create New...