Jump to content

Derbroomaster

Members
  • Posts

    116
  • Joined

  • Last visited

Everything posted by Derbroomaster

  1. I reported this in the main bugs thread. Doesn't seem to be gaining traction.
  2. I've experienced the yaw challenges described above, as well as a disruption in how keyboard inputs work for the Man Trk X and Y axes, and laser detents (first and second) I use an x-box controller via JoyToKey. The key inputs are being detected (I can see the knobs/buttons functioning in conjunction with my button presses), but no action occurs on the screen. The Man Trk axes are mapped to WASD and the LRFD detents are mapped to "." and "X" Track included. Note how little left rudder is needed for taking off. Apache Challenges 9-23-22.trk
  3. I re-saved your original file, then ensured the GU_MAIN_VIEWPORT was defined in the CustomMonitor.lua file. I'm happy to report I have a fully-functional AH-64D touchscreen, complete with George AI interfaces for both seats. Thank you Floyd1212 and Bunny for your help through all this. Your willingness to put up with my bumbling is the only reason this was possible. Cheers!
  4. Thanks very much for your feedback and patience. This is actually very fascinating, even if I'd like this to progress faster than it has. I've learned a great deal about .lua files and what things mean. I'll try another go round, this time ensuring I'm using a fresh copy of your Preston_AI file. I'll run it as-is, ensuring the reference you spotted isn't there, then make adjustments if I think they're necessary and report back. Thanks again.
  5. OK, thanks for that. I downloaded it and tried it as-is, but no luck. I did note the comment about the compass_pos being relative to screen center, with 1 meaning half screen height. So with that in mind, I altered the compass_pos and the weap_control_pos lines to fit on my 5760-wide screen (3 x 1920). I left what I presume to be the x values intact, but changed the y values to bring them up into the visible range. Sadly, I still can't see them. Thoughts?
  6. Understood. Do they all work? The one I've tried does not.
  7. Think you could share you Preston_AI .lua? I've got everything working except for the George AI interfaces. They work in my normal Helios profile, but not my Apache for some reason.
  8. OK, I made the corrections and the file is recognized. Thanks very much for yours and Bunny's assistance. I truly appreciate it. At this point it's simply a question of getting the outputs to the correct x,y parts of the screen, but I think I can handle that.
  9. As long as I'm playing DCS, I'm likely going to be editing .lua files, lol. Can't be a bad tool to have around.
  10. Yes. I'll get sublime today and try it out. I'm nowhere near being a coder, I'm just trying to get stuff to work ; ) Honestly, though, is that what would prevent a file from even being listed?
  11. I've attached two files. Both are located in the DCS.openbeta\config\MonitorSetup folder in the Saved Games directory. The Widowmkr Apache File shows as an eligible monitor profile in DCS. The other ("altered") file does not. The "altered" file was made re-typing all the lines AFTER line 1. Any and all feedback is welcome, please. Widowmkr Apache File-- altered.lua Widowmkr Apache File.lua
  12. Thanks very much. I'll take this advice today as I type it all out manually using an existing file that's recognized. Cheers.
  13. I'll give that a go tomorrow.
  14. Thank you for your response. Just spent an hour doing as you suggested. Unfortunately, nothing has changed. I cleaned up the spacing and semicolons. I renamed other files that work and they show up as choices in the drop-down box in DCS. No matter what I do, mine doesn't show up. This is maddening. I can understand playing around with x and y positions, but not showing up in the list when it's no different than the ones that work makes no sense at all to me. DCS Apache.lua
  15. OK. I've experimented further, but no progress. I tried copying everything in my Apache profile, then pasting into the Helios profile, which I know works. That did not do the trick. I'm sure the solution is something simple and I'll feel dumb when I finally get it, but I'm truly at a loss right now. I've uploaded two .lua files: One is my standard Helios monitor profile, which works and DCS shows as an available monitor profile in the setup menu. The other is the DCS Apache file I've edited. Both are saved in the Saved Games area under the DCS Open Beta config monitor setup folder. DCS Apache.lua Helios.lua
  16. I looked and looked and could not find a duplicate. I edited the "name = " field to something else anyway and it still does not show in the drop-down.
  17. Any idea why a profile would not show up if it's in this folder? I tried to see if there's something in the file that would render it unrecognizable, but I can't see anything. It shows the Helios profile but will not show the Apache profile that is in the same folder.
  18. Here's where I have it. DCS does not show it as an option in monitor setup. null
  19. Here's what the setup looks like to Windows. 2 is primary. There is no perceptible gap between 2 and 1.
  20. 3x 1920 x 1080 monitors stitched into 1 using nVidia control panel, then another 1920 x 1080 touchscreen below (Monitor 2).
  21. Thank you. Fixed that. Still not exporting, however. The Apache configuration doesn't show up in the Monitors list in Options. Apache.lua
  22. Repeatedly, yes. Something must not be registering for me.
  23. Hello there. If anyone has a .lua for the viewport exports to a 1920 x 1080 screen they could share, I'd greatly appreciate it. I have had no luck figuring out the export myself. Otherwise, this screen is very cool!
  24. FWIW, I have a 1920 x 1080 touchscreen. I have tried updating my Apache .lua to include all the defined viewports, but I'm not having any success. Updated file included. Anyone have a 1920 x 1080 touchscreen .lua they'd like to throw at me? Be my guest! Apache.lua
×
×
  • Create New...