Jump to content

Krondl

Members
  • Posts

    14
  • Joined

  • Last visited

About Krondl

  • Birthday June 28

Personal Information

  • Flight Simulators
    DCS
    IL2 - Great Battles
    FSX
    X-Plane 11
  • Location
    El Paso, TX US

Recent Profile Visitors

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

  1. The mission is stupid easy now. Not worth the bother, actually. It used to require power management, but now you can just yoink pitch and fly to the top of the mountain without climbing turns. Then, you can easily take off from the mountain top without beeping the governor to maximum. Never mind that there's no longer any clouds to consider. Yes it's easy, now. It wasn't when it was launched and the flight model and the weather system were challenging.
  2. DCS clouds look great. It's becoming apparent to me that AI pilots are not hindered by them. Please include the unfortunate option (as was the case regarding ArmA grass), to disable it, hence allowing player pilots to see as well as AI pilots.
  3. A-10C II doesn't have vibrations on Jet Seat. How to fix?
  4. Wrong. ED should simplify this. Tacca made a simple fix to allow people to adjust the 'NVG' relative to their 'eye' position on an ever changing platform. ED continues to ignore the fact that the NVGs obscure most of their instrument panels. Either ED happily ignores the fundamentals of NVG adjustment in favor of chasing a buck, or Tacca (while he was active here) was a better coder than the sum of ED.
  5. I'm not having any luck getting the NVG mod to work. The fact that a mod is necessary to be able to see the instrument panel should be an embarrassment to ED. While the depiction of what the world looks like under NVG isn't bad, never once in a thousand hours of NVG flying would I have taken off without first adjusting the tube position (upward in this case) to be able to see the panel. Should be a basic option to move the NVG circle up, and/or reduce it's vertical measure. Can't believe this is a difficult thing to do.
  6. Thank you for that! I didn't even think to find out if they had one :)
  7. I'd like to refocus on the laser ranging issue. I've been playing SP and the laser range will often report an unrealistic value. I usually check it before takeoff, but even after, the system will sometimes report a value less than 1000M when I'm lasing targets about 4KM out. Doesn't happen all the time. The range displayed will show as obviously inaccurate and will remain the same no matter where I point the left-seat camera prior to lasing. I find HOT 3 missiles self-destructing when the GPS says I'm at 3.8KM from my plot of the target coordinates, but the laser range gives me something erroneous like 286M. Is this still being tracked as an issue?
  8. May he rest in peace and his loved ones find comfort and grace. Very sorry for his untimely passing :(
  9. Re: my above post T-50 base with TMWH buttons... Initial impression is it's fixed via Universal Controller Remapper (which requires vJoy). Game Controllers properties is now showing correct DX button outputs. No time for a while to see if I can create a combined controller profile for BMS (like Mud's for T.A.R.G.E.T., etc.). Couple of observations in case someone else is looking at trying this: If vJoy is hanging on install, uninstall it (since the install didn't finish on the first go, uninstall wasn't straight-forward). Then make sure no other controllers are plugged in, and reinstall. Can't remember who wrote it, or what forum that fix was in. But might be worth recommending unplugging stuff prior to first install attempt. In vJoy, assign 1 continuous POV hat. I thought at first to use a 4-way hat since the POV1 was outputting 4 buttons. You'll only get Up, Down, Left, Right with a 4-way. Choose continuous to get all 8 points. Then in UCR, create a <remap button to button> plugin for Button 9 to hat1 -> up. Make plugins each for 10 ®, 11 (D), and 12 (L). The remainder of buttons are simple button to button plugins. Remember to do button 1 and the X, Y axes even though they are unchanged by using the T-50 base. The vJoy device will have no button 1 or axes if you don't.
  10. T-50 base with TMWH stick buttons all moved, any way to put them right? Hello all, I've posted this question in BMSForum and VirPil forums also. I'm trying to sort out the problem listed in the title. Apologies up front if this has been covered already, or if this is simple stuff to fix. I didn't find it, and I'm a bit short of simple. I've got a TM Warthog grip on a Virpil MongoosT-50 base and I love the way it feels. However, all the buttons are all moved (changes listed at bottom). I've poked a bit at solutions, but thought it wise to put it to the smart folks first. UJR, UCR, and Joystick Gremlin all seem (to my untrained eye) like they might spoof Win10 into seeing the TM grip with the same button assignments that the TM Warthog base would show. I suppose I could just reassign things in most titles to each button/hat direction, but I'd like to start off with buttons and hats as if I were using a TMWH base. Am I on the right track? Any recommendations for which software to use? I've read that keyjoy assigns keystrokes to button presses and has associated limitations (one button at a time only). Do UJR/UCR or Joystick Gremlin have similar limitations or to they have the effect of simply reassigning DX output for a given button press? Any advice would be most appreciated. Thanks in advance, Mack List of TM stick on TM base DX to TM stick on VPC base DX outputs: 1 -> 1 2 -> 3 3 -> 18 4 -> 19 5 -> 8 6 -> 2 7,8,9,10 (TMS) -> P.O.V 1 11 -> 13 12 -> 14 13 -> 15 14 -> 16 15 -> 4 16 -> 6 17 -> 5 18 -> 7 19 -> 17 P.O.V. 1 -> 9(U), 10 ®, 11 (D), 12 (L).
  11. Please disregard my previous. Found Notepad++ on a different thread after looking a bit more
  12. I want to give this a whirl, but have read somewhere not to use notepad to edit .lua files. What can I use for this instead? Much thanks for the suggestion
×
×
  • Create New...