Jump to content

darkman222

Members
  • Posts

    1068
  • Joined

  • Last visited

2 Followers

Personal Information

  • Flight Simulators
    DCS
    Falcon BMS
    MSFS 2020
    Strike Commander
  • Location
    Mainz / Germany

Recent Profile Visitors

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

  1. @BIGNEWY Can we please get a tag if it is being worked on or not? As soon as the ST exe will be taken away from us, we wont have any reference to test it with. It is definitely a MT issue here. Testing again with ST and no lags or spikes occurr on the CPU frame time graph. If there was MT optimisation done in the latest update it does not show up in improved performance in MT.
  2. The topic is "F16 performance in dogfight" and initially it was asked about outrating an F18. To which the answer is simple. You just cant outrate a player flown F18 in an F16 in DCS. About the question @MTMbrought up later in the discussion, outrating a Mig29 but not being able to sustain 21 degrees per seconds is related to when to utilize the max turn performance that is only available pulling 9G which is of course not sustainable in the F16. To make it clear to @MTM. Thats what my video should illustrate. You need to use the 21 degrees per second under 9G at certain points in the engagement for a certain amount of time. Which was a maximum of 13 seconds in the test I did. Just to compare it to the requested minimum of 15 seconds 9G tolerance for the DCS pilot which make total sense in watching my engagement flown with G effects off. This is even more important against an F18 that you cant outrate. When people talk about dogfight performance its just not only sustained turnrate that counts. I am pretty sure the OP is also happy if someone tells him not to just lock the stick at max sustained turn rate and wait.
  3. @MTM Although you can outrate the Mig as @BIGNEWYshowed, it took him 5,5 circles and 2 minutes to get into the control zone. You want to kill as quick as possible and not to be proud to maintain the perfect rate speed all the time until the wingman of the Mig killed you with a heater while you were doing your airshow. If you start with excess speed, climb, bleed the speed down to gain angles, then speed up again, and repeat: You can do it in 44 seconds for the first shot opportunity and you can be in his control zone after 3,5 circles or 1:20 minutes. Thats 40 seconds less for his wingman to potentially shoot you. But only if you DISABLE G effects. You can watch the tacview the track file creates and count the completed circles in each engagement. And watch the control indicator in the video how often I just go for full stick aft bleeding down my speed to gain angles. The thing why I am saying this is because people have the impression that the F16 is a bad dogfighter. This is not necessarly the case. The DCS pilot is bad and blacks out after a few seconds. So the only thing that remains as gameplan is to fly at rate speed not exceeding 8G to keep the DCS pilot awake. This thread is about the DCS F16 performance in dogfight. And if the pilot is the limiting factor for a jet that was designed to pull 9G with a reclined seat, I find it totally legit to bring the g modelling into this discussion... again. It is being worked on, I know. And in the respective threads there are documents that state that an F16 pilot needs to be certified for at least 15 seconds of 9G tolerance. If not even 30 seconds. How should you fly and win in a jet as it was designed to be flown with that limitation created by the DCS pilot. kill no sustained turning3.trk
  4. @BIGNEWY No! The stutters with aircraft coming close to the player are still there as before. The gazelle seems to have a good impact for testing. Another F16 does the same, but gives not that much of a CPU impact. As soon as I come close to the gazelle the CPU frame time goes up. Creating bad spikes in fpsVR which are visible as hefty stutters. Thats the yellow dashes in the GPU graph. Thats what looks like stutters in VR. Especially in dogfighting it is really annoying when youre close to your opponent when smooth playback is needed you end up in a stutter mess. See how the CPU frame time goes up every time DxDiag2_9.txt stutters gazelle.trk
  5. The thing is that its not just about rating around a bandit for 3 minutes and flying a nice air show. All of the tracks of the fights above wether its a kill or not took way too long. If there were other aircraft around you would not have the time for 8 or more circles. Especially a human opponent would not wait patiently for you to outrate him. If 7000 lbs of fuel in a dogfight is realistic or not. You decide. You came from a ground strike with 3 bags. Get ambushed. Punch your tanks. Now youre in a dogfight with 7000 lbs of fuel. Totally realistic. Would you decide to fight or to bug out? Possibly bug out. Thats also realistic. Not to choose to fight. If you decide to fight, be aware of that an F16 with full tanks needs a higher speed for optimal rate performance (460 kts) than a 3000 lbs fuel F16 Bignewy flew ( 420 kts). You also need to consider when to spend your energy. If youre just rating, it will take for ever. You need to use the speed and bleed it down to bring the nose on the bandit. That would have saved a lot of time. But currently in the G modelling you cant do that. If you rate around a bandit your pilot is way too exhausted to withstand the final pull to get the bandit in the HUD. So you have to rate around just endlessly as you cant pull him in the HUD exchanging speed for nose position. Also I noticed both of you did that with G effects off. Try it with g effects on. Like it is on public servers. Thats a whole new level now riding on the edge of conciousness
  6. Thats the entire point in this. ED cant model the F16 gear damage due to overspeed as there is no data available, so there is no overspeed damage. But how can they model the 9G or 13,5G regime for the pulled paddle, if there is no data. This is against their own philosophy.
  7. I am not interested in the whole "use the paddle or not" discussion, as we have been there 1000 times. The only thing I really want to know if there are EM charts of real F18 for the 9G regime? Dont care if its from swiss or what ever F18s. As the DCS F18 has been released so long ago the internet is flooded with EM diagrams of the DCS F18 version. I cant find one for the real thing.
  8. Arrived just now. Great Pedals so far. But I cant bring the full motion of the RZ axis, the main rudder axis, into play. Its set to 100% but they have 2 or 3 cm more travel until they hit their physical maxium travel. Would be nice to get a 1:1 resolution for very sensitve jets on the ground like the F16. I know, DCS axis tuning. But nope. That was the reason for pedals with that huge amount of travel, to get rid of any axis tuning. For the toe brakes it works just fine. I can use the entire travel range of them.
  9. It really seems to need the quick "off parameter" part to it. 9.1 G is not what the jet is rated for. Interesting tho that this small amount of over G already is enough to induce the oscillations.
  10. I am particularly interested if it turns out that the drag is the cause for that...
  11. Use DTC for DCS instead. In the F16 you can long press the WX button on the ICP that will start the upload to jet process. https://github.com/the-paid-actor/dcs-dtc
  12. Dude. Without a video or track file, nobody will be able to help you. This just sounds like a double bound hotas button, switching something off while landing, that messes up your alignment.
  13. Exactly. No loadout and low fuel state. Its still there.
  14. Its not that the wobbling oscillations should not happen at all. But once they start in the lateral axis, it wont stop unless you stop pulling. Not really sure if thats intended.
  15. Why is the the F18 with the FM update still oscillating left and right, when rolling and pulling up right after that? I thought I heared this would be adressed as well with the update? Or will that behavior stay because its realistic?
×
×
  • Create New...