Jump to content

Low Blow

Members
  • Posts

    208
  • Joined

  • Last visited

Posts posted by Low Blow

  1. We did some testing on NTTR with a clean viper on the deck in two circle against a clean hornet (both at 75% fuel) and the viper couldn't maintain 360 KIAS at 6.3G while the hornet had no problem whatsoever. Not going to say who the other guy with me was but we both agreed that the Viper feels like it is drastically underperforming in the rate war right now. It simply does not have the ability to outrate the hornet which is absurd.

  2. Ok I'm pulling my hair out with this program now. I cannot for the life of me figure out what is going wrong. I attempt to run the installer after extracting the zip and nothing happens. So then I follow the readme.txt and manually install all the luas etc then attempt to run the client (which has opus in the same folder). I then see the SRS icon appear in my tool tray momentarily but the INSTANT I go to click it by hovering my mouse over it, it disappears. Ciribob I've sent you a message on ed forums about this. WHAT IS GOING ON please?

  3. Black flashes have returned similar to what we were getting with Rift CV1 a few months back. Last night during low level return to carrier, within 5 miles of CVN group started getting brief black flashes in Rift S. Anyone else getting this?

  4. I always try to perform a 'military landing', whether an adjusted F18 one for practice like this:

     

    takeoff from deck

    flapsUp GearUp

    180°

    @600ft@~250-300kts

    reaching abeam gearDWN

    hard bank base into final

    brake by pitching

    Flaps Full are down @ 90°

    estimate/calculate ‘on speed’ by examining trimming bracket

    past 45° final be at 170kts, cut throttle

    level off @320-350ft 'on speed' short final @132-135kts, on the ILS if On

    catch 3 wire

     

    Or,

     

    the documented actual one (flown in F14 by flight leader only, but here in F18C)

     

    5NM@5000ft@550-650kts@30°CW left of ship heading 30° of Stennis sails N

    fast speed decent 'to the LSO position' @600-1000ft, @580-650kts

    over the LSO hard left bank

    pull as much G's as 1% of speed (650 slowing down to ~350kts)

    end up 30° wide (250°, if Stennis heading N)@~1.5/2nm TCN

    never level off in the whole pattern

    speedbreak only if miscalculated, you should do without

    @~350kts abeam (still wide) start the measured circling with less bank, into to final

    lower gear@280kts

    1st flaps passing 220kts full flaps passing 185kts

    passing 90°-45° 'trim on speed' bracket

    catch 3 wire

     

    (Dotted down by memory, not tested line-by-line)

     

    Not mentioned in NATOPS

     

    NATOPS is for pussies.

     

    Sorry mate it is a bit hard to take you seriously when you make statements like "NATOPS is for pussies" then in another thread on here you are asking whether the military use NOTAMs. Maybe just keep your opinions to yourself if you have no idea what you are talking about.

  5. Hi Felix,

     

    Your setup will run DCS well in the rift. I have the rift and a setup nearly the same as yours (only difference is the processor) and I fly in the rift with a great experience.

     

    I have owned the TM warthog for 6 years and it is still going strong. You may just want to open her up after a couple of years and re-grease the gimbal with marine-grade grease. You can find several videos on YouTube that document the process.

     

    As for pedals, depends on your budget. Saitek combat pedals are good at the budget end but I don't believe they are in production anymore. TM have a very tasty looking expensive option coming out around now or in the very near future.

  6. Hi Heatblur,

     

    You've done a fantastic job with the cat. Straight out of the EA box it is excellent. The only small request that me and some of the people I fly with have is for a version of the pit with far less wear and tear please. I understand that pits get worn but the amount of wear on the version you have released is to the point where without mousing over certain switches the printed labels give you nearly zero chance of being able to identify what the switch does. This becomes even more true when in VR.

     

    I am aware that there are likely to be some posters who will jump on here and tell me to get better in the cat so that I can use those switches without having to mouse over them first or read the printed labels, and believe me when I say that I understand where they are coming from with that sentiment. However, a real jet with switch position labels that are completely worn off would probably have a new label written back on so the crew could identify the correct switch selection.

     

    This pit imo looks like one ready for the bone yard as opposed to a pit 2, 5 or even 10 years into its service life.

     

    Again, magnificent job and hats off, however a newer pit would be greatly appreciated.

     

    Thanks

    LB :thumbup:

  7. Usually extend to drag bandit towards friendlies and "ABC" (always be climbing). Usually a bad idea to re-engage if you are low and slow. I generally wouldn't re-engage on a public server unless I have extended out, reset to 26K feet and gotten some SA back. If you re-engage when you are "tumbleweed" if probably won't end well. Watch for R73 / R27 ET as you turn back hot as obviously you won't get an audible warning. The point made above about setting your radar and possibly HMD up for where you expect the bandit to be when you turn hot is sound. Remember LHAQ (long press on sensor fwd) is good for up to 10 miles 80 degrees off your nose. I have achieved lock at 11nm in this mode however.

  8. I'm happy to pay full price for Early Access if the devs are responsive and proactive during the EA period. Without naming names, recently there has been one very high profile dev who in my opinion has dropped the ball in this area and is losing the trust of me and many of the people I fly with for that particular module.

     

    When they then release a new module without having proactively addressed their customer concerns or even communicating simple acknowledgement of a serious issue with a prior EA module this does not inspire wallet-opening confidence.

     

    In other words, why should I pay full price if you won't fix glaring and widely acknowledged problems with your EA module? Not even so much as a satisfactory response to issues raised by MANY customers regarding the same issue. In what other line of work is that acceptable? Put another way, early backers of this particular module got slapped in the face. They paid the highest price and had to tolerate being literally ignored. Yet someone who comes along a year and a half after release pays half price and doesn't have to deal with any of that.

     

    I agree, put an 18 month time limit on EA status. If they can't pull it out of EA by then then they shouldn't be allowed to release more EA modules.

  9. pretty much sum's it up.

     

    +1

     

    I had to fire up my monitor and track IR to test streamlabs OBS as streaming in VR is still a no go (affects in-game performance too much to be fun - you can check my specs below). Literally could not wait to go back to my rift.

     

    Despite the loss of resolution, VR just brings too much to the table for the type of flying I do these days. Your brain will learn where to click in the cockpit for your start ups so that you don't need to read what the labels say.

     

    If you are heavily into mk I eyeball CAS then VR might hinder you a bit too much though. If you are using a targeting pod then no worries, go for VR and you will be loving life.

  10. At the very least wait for a sale.

     

    Bugs are rampant, a lot of features are missing. A lot of people mistake bugs and unfinished systems for not knowing how they work.

     

    The thing is, almost every single mission the Harrier is supposed to do is completely or partially blocked by a bug or a missing feature. Examples:

     

    CAS: TPOD is extremely buggy. Not only can you not slave the TPOD to a waypoint or the A/C line of sight (the opposite is true, but really buggy, as soon as you designate the TPOD changes for the DMT page and you loose your TPOD picture), but moving target track is not working, the laser designation is extremely limited in range (compared to IRL counterpart). Moreover, the inertia of asymetric load is absolutely ridiculous and overdone (according to RL Harrier pilots) making it hard to stay on station while pickling off one GBU at a time. On top of that, the CAS page isn’t implemented, as is the CAS Datalink that the JTAC are supposed to be using. That, with a broken coordinate input system (unable to input a waypoint if no waypoint are present at first, no "precise" decimal waypoints as is required for accurate weapon delivery) and no JDAM makes for a hard time doing modern CAS.

     

    Low level strike: AUTO bombing symbology is simply broken and unhelpful. One of the most useful feature of the Harrier for low level delivery (CCIP to AUTO designation) is not implemented.

     

    Night strike: broken FLIR, no hotspot tracker, no NAVFLIR calibration means you can’t even CCIP correctly.

     

    Battlefield Air Interdiction: the Maverick implementation is extremely broken in the Harrier. No ground stabilize, no IR Cool switch functionality and you can’t even align the seeker without losing a MFCD for 3 minutes (because as soon as you change the page, it resets it). No TPOD to Mav handoff because of the broken TPOD. Controlling the seeker is actually extremely buggy, because you have to have the seeker page on the left MFCD to control it but it appears by default on the right MFCD (where it shouldn’t even show at all IRL).

     

    And yeah, it could be a pretty good module if Razbam actually did something. But it’s been in the dark for the last 6 months (ie no new features, extremely minor bug fixes). Even their bugtracker is updated maybe once per month, at tops.

     

    Would not recommend, certainly not at full price.

     

    +1 except I would recommend it if the Devs were more active in squashing the bugs that their customers have been bringing to their attention for over a year now. The most glaring example of this is their outright refusal to acknowledge or provide us with any kind of meaningful response regarding the clearly incorrect implementation of the auto bombing cue (PIBL) which in its current form is not ground stabilised and extremely difficult to use.

  11. Hyper realism is the hallmark of DCS, it’s what separates it from other games and sims.

     

     

    Not true. DCS is a game and you are kidding yourself if you think any different. And yes I flew military hardware. There are many, many things about DCS that don't fit into the hyper-realistic category. Bring on the Litening pod.

  12. Right. So why even ask in the first place?

     

    Wow someone needs to chill. Here's an idea. If you don't have something constructive to add to a thread then just keep it to yourself. You clearly just enjoy flaming/posting useless words. Read my signature for some life tips there mate. My OP was perfectly reasonable.

×
×
  • Create New...