Jump to content

heloguy

Members
  • Posts

    626
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by heloguy

  1. Appreciate the work on this. I'm trying to get the elevation data, but this link"https://dwtkns.com/srtm30m." doesn't seem to be working anymore. I did register on the NASA site, but I only get "404 NOT FOUND" when I use the link. I also don't have a telegram account, so I don't seem to be able to download from your page. Edit: Disregard. The link indeed doesn't work for me, but if I do a web search for a 30m SRTM tile downloader, I'm able to navigate to the page. Thanks again!
  2. Funny, this discussion was just being had in a Discord channel. MGRS accuracy is based on how many digits. A 10 digit grid is accurate to 1m. An 8 digit grid is accurate to 10m, and is what the 64 receives on the KU. Whether or not you decide to round depends on how accurate you care to be. Example: 37SDA2667733703 is the actual location on the ground you want to nav/slew to. If you round, the grid would be input as 37SDA26683370, which is 3m off in northing and easting. If you don't and just truncate, it would be 37SDA26673370, which is 7m off in easting, and 3m off in northing. Obviously, if there's a 5 on the end, it's pretty much a toss up on which is more accurate, but, my OCD makes me round.
  3. Got it, thanks. Probably try without speeding up the time and see if it happens again.
  4. Thanks, I understand that. I'm wondering if the fact that the sim's 3d world froze, but would still let me access the menu via the escape key is related to the bug mentioned in your previous post that the original poster was talking about. Basically, is it worth continuing to play, or is this going to happen on every mission until the bug is fixed?
  5. Just started this one and played through MSN 1. Had a pretty big FPS drop when the bomber formation spawned that lasted until after we turned back to base. After dogfighting, and getting a couple of kills, we were formed up and RTB’ing when the sim froze. I was admittedly accelerating time. Oddly enough, I was able to hit escape, and get to the menu. After trying to ‘RESUME’ a couple of times, only to have it freeze, I ended the mission. My kills were registered, but I only received a score of 50 for not making it home. Is this related to the issue described above? Or related to me using time acceleration?
  6. First of all, thanks for sharing this. I'm having a hard time getting this to work. I'm using OMM to install. I have Quaggles injector installed in \Saved Games\DCS\Scripts\Input, and I have your default.lua installed in \Saved Games\DCS\InputCommands\AH-64D\Input\AH-64D_PLT\joystick. I'm not seeing a "Special" category, or a "CPG Con" category as shown in the .lua. Edit: Nevermind, figured it out. I was installing the mod to the Saved Games instead of the main folder. All good now. Thanks again!
  7. I've tried several times now to load up the KW at night, turn on NVGs, the ODA in the right seat, and then enable the HSD on the co-pilot's side. Every time this results in a CTD when I press the HSD button on the left MFD. dcs.log
  8. Since the last patch, really appreciate the smoothness of the TADS and PNVS at night, but it looks like the original bug of them being roll stabilized when you tilt your head is back. See attached track. You'll notice that when I look at the extreme right or left with the PNVS, there's a point where the behavior is correct, but then it reverts to being roll stabilized. AH-64 PNVS_TADS Roll Stabilized.trk
  9. Really would be great to have this effect. It's a game changer, especially for any cargo/utility/assault aircraft. If anyone can't land in the dust doing one of those three missions, then they are basically useless pilots in the desert. Not too far off for attack pilots either, if they have to go to a dusty FARP.
  10. Yeah, that's the one you use if you have a FFB stick.
  11. I had to go to "FFB Tune," swap the axes, and invert the y-axis.
  12. If it's working, then you installed it correctly. If you don't have it installed correctly, you will not see it in the game.
  13. It should look something like this: X:\Users\<username>\Saved Games\DCS\Mods\aircraft\UH-60L
  14. Got an answer back from Pimax. They said they will eventually refill the 15mm foam pad. No timeline given. Thanks for that! I actually ordered that one, and I'm waiting on it now. Hopefully it gives enough clearance with prescription lenses.
  15. The rotors turn counter clockwise. This is normal for a US helicopter.
  16. I tried this morning, no answer. I'll try again, I guess.
  17. Only issue I have with that is there is no forehead portion. Is this confirmation that the 15mm face pad is discontinued, or just temporarily unavailable?
  18. Is the 15mm face pad discontinued? I'm waiting on prescription lenses to arrive, and I'm worried that the 11mm pad is too thin. I my eyelashes already brush the lenses with the headset on. Tried to ask on the Pimax website, but no answer through the live chat.
  19. Right Ctrl + Enter Left Win + M
  20. So, I do not have the MB339, and I've uninstalled the Gazelle, as well as all of my mods, and I still can't get the app to open. Disregard. Not sure why, but all of my Kneeboard folders in the main install\mods\terrains were not named correctly, even after a repair. I fixed the names, and was able to get the builder open.
  21. Quick shout out to say thanks. I have two WH throttles, each with the mod, and one a year older than the other. The oldest one is going on 6 years old, and they are both going strong. Wouldn't have a WH throttle without this. Thanks!
  22. I just set this up again after moving to a new computer with my rig. I had to change the values as I reversed the throttle axis in the Virpil software, but it's working fine.
  23. Yeah, it is weird. In the F-15E, when I trim with DX FFB turned on, I see the stick move in game, but it doesn't feel like my physical joystick is moving. I've used hardware trim on my Brunner in the past, and thinking of going back to it, as that seems more realistic.
  24. I've noticed this with the A-10, and with the Heatblur F-14, but does anyone else find the forward stick offset/bias a little excessive with DX FFB enabled? If I don't use DX FFB, then the stick stays in what feels like a more natural neutral position, but if I enable DX FFB, then the stick jumps forward, with no real difference in what the sim registers as control input. Basically, it feels as if it's simulating less stick travel forward then back, but the effect makes me have to sit really far forward in my simpit to grasp the control grip. Is there any way to use DX FFB, and have the stick not be in such a forward biased position?
×
×
  • Create New...