Jump to content

TacoGrease

Members
  • Posts

    184
  • Joined

  • Last visited

Posts posted by TacoGrease

  1. Could you please describe how? :)

     

    I use the slider axis on my Warthog throttle as the zoom axis in 2D and in VR.

    In 2D the axis is assigned to the Zoom axis in the game itself.

    But this doesn't work in VR.

    For VR i assign both VR zooms through Target to a range on the same axis.

     

    // VR Zoom on Slider Axis

    KeyAxis(&Throttle, THR_FC, 0, AXMAP2(LIST(0,15,16,39,40,100), VR_Zoom_Magnifier, 0, VR_Zoom, 0, 0));

     

    So while in 2D the axis works as Zoom axis (and the VR zoom binds are useless) but once in VR this doesn't work and then the VR Zoom binds come into play on the same axis.

    Range: 0-15% of axis travel: VRZoomMagnifier, 16-39%: VRZoom, 40-100%: Normal view.

     

     

  2. It’s especially fun even after the results of the Fight for Honor tournament :P

     

    Arguing about the capabilities of the Phoenix is essentially identical to arguing with people about the ACM prowess of the Tomcat.

     

    There are people out there that simply refuse to believe what they're being told despite all the hard evidence to the contrary.

  3. True, but it would be nice to hear from HB on this. It’s the most detailed aircraft in the game, so not being able to film something as basic/integral as Case Is is massively disappointing.

     

     

    It's more complex than that. The Fw190 A-8 suffers from the same problems. Client/SP replays never work but server replays work flawlessly. I've experienced the same in the Viggen a couple of years ago. I've also experienced it in the Spit last year, though the Spit seems to be fixed. None of those three aircraft have Jester/Iceman, but you may be on to something about the cockpit being the common denominator here.

     

    In its current state, the Tomcat just isn't good for filming. It's okay-ish for pure flight, but wing vapor isn't synced over MP so your server track won't show the vapor at all, and control surfaces are extremely jerky when they move. When taxiing on deck the wheels spin at about 30mph while the jet lurches back and forth, moving forward at about 3mph. When trapping the wheels sink into the deck, then the plane bounces about 5ft off the deck, and rubber-bands backwards. When landing on shore the wheels also sink into the runway at touchdown, then pop back up. These are all ED issues that they will probably never address.

  4. Through tests with the F-14 and F/A-18, I believe that Jester (and/or Iceman) breaks DCS replays.

     

    I will start by saying that, obviously, replays generally in DCS are quite buggy - no need to reiterate that.

     

    However, this appears especially true for the F-14B.

     

    I have run simple missions (for example, the Heatblur F-14B Caucasus Case I) about a dozen times in singleplayer, and the replays do not work for any of them - even when no time manipulation (e.g. speed up, pause, slow down) is done.

     

    By comparison, such replays for simple missions with the F/A-18C work FLAWLESSLY.

     

    So, why Jester/Iceman?

     

    When I run such a simple mission on a server and obtain the server track, the replay works FLAWLESSLY - just as with the F/A-18C tracks. Jester/client data is not present in the server track (evidenced by no F1/cockpit view of the aircraft on a server track).

     

    To conclude: F/A-18C client and server tracks appear to work with simple/short missions, whereas only F-14B server tracks work. I believe this strongly points to Jester data breaking client tracks.

×
×
  • Create New...