Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by 104th_Maverick

  1. On the TSD page the wind reading you get is reversed from what you get in the mission.  If you notice on the screen shot attached the wind read out on the aircraft says its coming from the West however the wind sock is indicating the wind is coming from the East (check ihads heading tape).  After flying the aircraft I confirmed that the wind was indeed coming from the East after cross checking the airspeed vs ground speed.


  2. Please guys, I don't mean to be a total layman but surely this can't be a lot of work to implement into the stream.

    Currently we are using containers as substitutes and they look ok but we really need HESCO barriers to take our FARPS/Camps to the next level.  There are some fantastic mods available with HESCO Barriers but this kind of thing in the core game would be hugely beneficial to the whole community without the need to go out and installed mods.hesco-bastion


    • Like 5
  3. Thanks for the all the positive feedback guys, although I have to confess I think I may have accidentally misled some of you.

    The footage from the start of the video where the aircraft is not moving at all is when I have 'Active Pause' engaged to enable me to explain what is going on and show you the cockpit displays, sadly I'm not that good just yet that I can maintain an absolutely perfect hover.

    I am doing the hovering manually however after the first missile shot without Active Pause engaged using trim and very small input adjustments.

  4. +1 on this.

    While I 100% appreciate its going to get easier with time to master the trim its just too easy to get yourself in a horrible mess, particularly when you're changing flight regimes to and from the hover as our sticks at home don't stay in the same position as the real aircraft does when force trim is used.

    • Like 2
    • Thanks 2
  5. Heard from an Apache pilot that when the front seat selects the Hellfire the Laser should 'power' on with the missile (not fire). 

    Current implementation means that in Multiplayer the CPG has to manually turn the laser ON before firing it by going to WPS - UTIL - LSR and making sure the circle is solid next to the Laser selection, which is causing a lot of confusion because this is not mentioned anywhere in any manuals.

    • Like 1
  6. On 12/2/2021 at 4:41 PM, Hulkbust44 said:

    Except his understanding of TWS vs RWS for the Hornet is all wrong. I'll post my comment on the video here.

    "You seem to have a fundamental misunderstanding of TWS vs RWS in the Hornet.

    First, the whole thing about RWR warnings for the bandit. There is NO difference between RWS and TWS. A STT is a STT. A L+S designation is the same "soft lock" in RWS and TWS.

    Next, there is no difference in trackfile processing. Hornet RWS functions exactly like TWS aside from the auto scan centering (DCSism). RWS just dosen't have frame refresh minimums and will only display HAFUs for a few trackfiles. (And a TUC) Advantage of RWS is larger scan volumes, less cluttered displays. You can always just use NWS to step through ranked trackfiles.

    The thing is, in DCS the Hornet A/A logic is not right in basically anyway.

    The aircraft is lacking Multi-Source Integration (MSI). This is a special type of sensor fusion the process all available data to create a track file. The radar is just one (still a primary) sensor that contributes. Other possible contributing sources: donor DL trackfiles, EW suite, ATFLIR, IFF, and HARM. With this, you can designate and fire on tracks without radar contribution. There should be no track display difference between Attack, SA, and AZ/EL formats. You can designate tracks via SA and whatnot. Not to mention that an AMRAAM launch should cue TWS AUTO and command RDR priority."

    The video is alright...he does a lot of unnecessary things and didn't mention some of the current radar issues and workarounds. Namely hit age out affecting trackfiles.




     I don't have any misunderstandings of TWS vs RWS, I was referring to people engaging in RWS using STT.  I never once talk about going STT using TWS yet you bang on about it being the same in TWS and RWS like you think you're teaching me something in some hyper critical manner.

    I was also giving people advice on how to use the Hornet radar in 'DCS' as we have it, not how you think it's supposed to work in real life, again you seem to have gone off on some nonsensical random tangent ranting on about things I never even mentioned.

    The video has helped literally 1000s of people who have given me loads of positive feedback on how it has improved their experience using the radar.  It's a tutorial on the way I use the radar as a GAMER not as a fighter pilot and the way I demonstrate it works perfectly well and people will get results from it.

    The methods shown in the video work, no amount of nit picking will change that, I set out to help people use the radar better and I did just that, you can stop your little crusade now.

    • Like 13
    • Thanks 3
  7. To add to this, there seems to also be an issue with Red F-16s getting PPLI to work.


    In one of our missions (Operation Blowdown) PPLI works perfectly well for the F-16 for clients that join in the same group.  For another mission (Operation Northern Storm) clients who join the same group CANNOT get PPLI to work despite both missions have the aircraft set up identically.

    I have even tried moving the EPLRS from Advanced Action 2 to Advanced Action 1 with no joy.


    To recreate this get two clients.


    Join the same F-16 group on Operation Blowdown and observe that PPLI works between both fighters when aircraft is powered up, you see wingman is blue once alignment is complete.


    Now join the same group on Operation Northern Storm and observe that even though both clients are in the SAME group, PPLI does not work



  8. For some reason clients that are flying Red aircraft on the US Aggressor coalition get degraded datalink performance from the AWACS in game.


    If you place a BLUE client X nm away from a Red AWACS he WILL see the enemy AWACS on datalink,

    If you place a RED client X nm away from a Blue AWACS he will NOT see the enemy AWACS on datalink.


    I have attached a mission where you can clearly see this problem in action.  Simply join the Blue hornet slot and look at the SA page, you will see 3 friendly AWACS and 3 enemy AWACS on SA.

    Now join the Red Hornet slot and you will only see 3 friendly AWACS and no enemy AWACS despite the enemy aircraft being well within range to be picked up by the Red AWACS and info displayed on Datalink. 



    I have also attached some screen shots (2nd post), you can clearly see the Blue Datalink shows the enemy aircraft but the Red Datalink does not. 


    Red datalink.png

    Blue datalink.png

  9. Totally agree with BonerCat, the Viggen is more than capable of pulling off this mission, it's a little ludicrous for you to say something like 'please check what the Viggen is capable of before putting them in a mission like that' when this type of mission is exactly what the Viggen was intended to do.


    You obviously did not enjoy the event and that is understandable, if you had fighter escorts the outcome could have been very different but please do not try to blame the mission designer for your failure.  Bullet did a fantastic job and your aircraft was more than capable to get the job done, things just didn't go your way.

  10. 20 hours ago, Yambo said:

    [51☭] PVO / [100☭] KIAP  - Red Navy  8xSu-33













    You cannot sign up others brother, you can only sign up from your own account for yourself, if those people want to take part they will need to sign up quickly 😉

  11. Curses! I'd recommend using zoom to help you then sir, while not ideal, it could help to zoom in further than you would normally do so you can see the ball and start ball flying as soon as you get in the groove, then approaching the ramp zoom out to your normal zoom level.

  • Create New...