Jump to content


  • Content Count

  • Joined

  • Last visited

About randomTOTEN

  • Rank
    Senior Member
  • Birthday 08/27/1985

Personal Information

  • Flight Simulators
    DCS World
    Microsoft Flight Simulator 3.0/4.0/X+Acceleration
  • Location
  • Interests
    Cycling, Computers, Aviation History
  • Occupation
    14CFR121.533(&535)b,d,e. E-170/175

Recent Profile Visitors

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

  1. So your entire thread is invalidated because you misjudged the density altitude?
  2. I don't agree with this. I don't believe you were in VRS until less than 35m AGL on the file "2.trk" I tested this by taking control and attempting recoveries by increasing collective hard. If you were in VRS this would have no effect. The lowest I can recover by increasing collective is 35m. I judge that you were never in VRS above 35m. 2trk recover 35m agl.trk I controlled view and simulation rate earlier. When Radio altimeter indicates 35m I hit "Escape" key on keyboard, and select "Take Control" EDIT: I also think you compound the analysis
  3. I think you did find VRS paramteters on your final attempt. But you're the helicopter pilot, you can judge these values probably better than I can. You also make analysis hard here. I have no output of raw flight data (no Tacview), and am forced to rely on cockpit instruments. You fly this test like a pilot, and not a test pilot. You are trying to replicate landing attempts that end in VRS. My example shows my attempt to maintain steady flight parameters to compare them to the stated "impossible to perform in DCS" condition. But that simulator flight was also read off instruments.
  4. I'll be gone for 2 days, but will try and watch when I get back.
  5. I think mine does too. And I get to nearly -5m/s for a moment there. EDIT: I also judge that he has begun to loose tail rotor control at that point. Something we don't have. Also, did you notice the airport is Sochi-Adler?
  6. I think the more relevant time stamp is actually 3 minutes, 42 seconds. It's immediately before he enters LTE (which I would love to have modeled.) From my viewing, it is the moment where the horizontal IAS is the lowest, and the VSI is simultaneously the highest. I.E. the best candidate for VRS. If I'm reading the instruments correctly, at 3:30 the KmIAS is 100. Vertical speed -4mps. At my time stamp the values are about 60kmIAS and -4mps. Let me know if you think that's a more severe example. I think it is, but I have 0 RL rotor time. My time stamp values translate to 32 KnotsIAS
  7. You can try searching your computer (DCS folder if you know where it is ) for the file named "DCS World Input Controller Walk Through EN.pdf" I think that's what you're asking for.
  8. I also agree this is likely the problem. For the MiG-29 too. These landings should probably overload the NLG to the point of failure, but as the gear doesn't fail, the physics simulation tries to process the overwhelming forces anyways, which results in the excessive spring back into the air.
  9. yeah that happens with long tracks, meanwhile every other track posted in this thread (that I downloaded) works beautifully You don't know that. It's entirely possible that what sent you back bouncing into the air was a collision with some mod object on the airfield, that's probably nowhere close to your landing point. Things like this are why tracks are useful.
  10. It fails to load because I miss the following mods: VPC Object by voc & Virpil.com Ala13 Pack I do have VPC airfield equipment mod if that's what "VPC Object by voc" is, but I don't know if we have the same version. I don't know what "Virpil.com Ala13 Pack" is. It's also possible that these mods are what was causing the problem for you and your squad mates (especially considering they were using the same mods). So that's another avenue of investigation. Can you create a simple (and short) mission (with the mods disabled) and try to recreate it? That's really what I wa
  11. We don't know what you're talking about because you didn't upload a track. CoBlue might not like our analysis of his tracks, but at least he uploaded them. We can carefully examine each one, and take control of it and test it for ourselves. These tracks are worth about 5 million words each. People can hate them when they try to use it as a replay system, but for "seeing what you saw" they are fantastic. Much better than, "well it happened to me and all my buddies, why aren't you guys seeing it?" Recreate it and upload it here. If you can't... well then that's valuable i
  12. To help demonstrate just how hard the smack really was, I changed the view of "mig21 land 1.trk" and moved the free camera to approximate the perspective seen in the timestamped youtube clip, "Mig-21 landing on a highway" of course I can't replicate the telephoto effect which compresses the perception of distance, so I'm a little closer to the touchdown point than the videographer. mig21 land 1 Youtube View .trk
  13. You came down like a sack of bricks, ripped the fuel tank off on at least 2 of the tracks. These were not "a little hard." You should have blown tires on these (if that was modeled). Vertical speed nowhere close to the the video footage. Simulator pilots are a terrible judge of sink rates on touchdown. You bounce because you bash the nose wheel. Just like when people complained about the 29. They bashed the nose wheel too. Stop bashing the nosewheel and you'll stop bouncing like that. Watch your source videos. They don't bash the nosewheel. Watch for smoke from the nosewh
  14. Thank you! Curious, do you know why there are two green R's, instead of just one?
  • Create New...