Condor_USAF

Great advice mate. As an aside, ausairpower.net is the single most comprehensive, detailed, and technical site I've ever found related to air combat weapon systems. Seriously, the level of detail in there is astonishing (something you'd expect from Jane's or RAND), and I cannot believe it's unclassified let alone available for free. Hats off to Dr. Kopp! As an aside, my username really should have said Condor_RAAF but too late now :thumbup:

This. Throttle to idle is standard spin recovery in ALL aircraft. A stalling, spinning aircraft expelling thrust is akin to a balloon with the mouth freed...it'll only serve to throw the aircraft around all over the place. Better to allow the vehicle to settle into its lowest axial energy state (i.e. a straight dive), regain optimum alpha and airspeed, and recover from there.

Additionally, control surface throws are supplemented in high performance aircraft, such as with aileron spades in aerobatic aircraft and of course extremely fast response hydrualic actuators on jets. Plus relaxed static stability by design, literally breathing on the stick makes the aircraft react instantly. 30 minutes of flying on an Extra 300L was stressful as heck, the aircraft demanded complete attention at all times, and anticipation and instant reaction time. It would be an order of magnitude more intense in a fighter.

I want to agree with you on this, and certainly there are no reports of pilots even approaching anything remotely close to a blackout on launches. But what we don't know is how many g's the DCS model is simulating during these heavy launches. Maybe it's (erroneously) simulating something stupid large like 40g instantaneous impulse force, which wouldn't happen in real life but IF it did, that can cause a brief blackout. So looks like DCS physics model is still very detailed, just needs to be reconfigured to more realistic tolerances.

Except that 'yaw' is also an aerodynamic term. Whilst on the ground during taxi, it's just a 'turn' (I've never heard any pilot refer to a taxiing turn as yawing).

Wow, crazy that DCS has modeled realism to this extent.

Not to be pedantic, but this isn't Adverse Yaw at all. AY is a purely aerodynamic phenomenon, manifesting only in flight. While the aircraft's movement in the horizontal plane is similar in OP's scenario, adverse yaw it is not.

A C172 is just a powered glider, literally a canoe in the sky. Massive static stability advantage by design, it will literally fight to stay stable. MUCH different experience in a high performance aircraft with similar power/weight stats for e.g. Extra 300 et al. THEN when you get into jets, it's a compleeeeetely different ball game, LET ALONE a fighter jet

Ahh, here's comes the edgelord who can see the reeeeal truth that no one else can. :doh: No need to apologise, literally NO ONE cares whether you buy it or not. Obviously you haven't made the effort to read any of the previous comments, where multiple posters have explained very well why OP or anyone in a similar situation would rather not go through the trouble of an unwarranted investigation and the potential risks it entails, however minuscule, DESPITE having followed every rule in the book. Right. Because you know in detail what qualifies as OPSEC, falls under each Security Clearance classification, and have a thorough understanding of the UCMJ and its protocols...right? Kthanxbye.

Spot on!

Yeah, nah. I flew MS Flight Sim and X Plane for 15 years, and the first time I flew in a 2 seat Extra 300 and Pitts S2A, I felt like a fish completely out of water. Heck, I felt like that even on my 5th time. That's because no sim, with even the most powerful graphics setup and VR, can come close to recreating the limbic system experience, and thus your reactions to the aircraft's movements would be nothing like they are on the sim. This would be true in Cessna, let alone in a uber high performance fighter jet. It's like if you'd never driven a motor vehicle before, I don't care how great a car/truck simulator you might have used, you're got going to be able drive one in real life unassisted the first time. At BEST you could startup and taxi at low speeds. Takeoff and land, forget about it....even with minimal g loads and flying like a grandma. Back to topic, I think we all enjoy such comparison testimonials from real life pilots because they validate our simulated experience. And no doubt DCS is extremely high fidelity ('study' sim level). But a simulation inexorably bounded to the audio-visual media, no more.

Ahh that explains it, yes flying in a thunderstorm would make a yaw-indicating HUD go beserk haha. Thanks!

Thans man, the TACAN and ICLS are now working. The HUD however, is still an issue (please see attached screenshot). I"ll take a track for you this weekend, but I'm doing a startup exactly as stated in training and Chuck's manual. The only HUD related control I touch is the brightness, and I do set the INS to CV (If that makes a difference). I tried another mission with a hot start (the first waypoint in the air), and same result. :huh: Thanks. Weirdly still, Stennis will now talk to me when I request inbound/landing, but still ignores me when I request startup/takeoff. :(

Hi guys, I've setup a Case 3 sortie in the mission editor, taking off from the carrier - cold and dark, waypointing to and landing at Sochi. Then taking off again and landing at Stennis in a thunderstorm at night. Here are the issues I'm facing: 1. I have set Stennis' comm to 127500 FM in the mission editor. Yet when I set my aircraft's comm 1 (or even comm 2) to that frequency and request startup/takeoff, I get no response. I do however get response from the ground grew, and even from Sochi ATC when I switch my frequency to Sochi's 127000. 2. The HUD acts funky throughout the flight. The symbology will randomly drift way to the left or right, so that I have to move my pilot's neck laterally to read the data points at the far end such as the distance to next waypoint. The velocity vector meanwhile will drift to the other end so that it's barely in view, so its very difficult to align it with the horizon or pitch ladder. 3. I also have Stennis' TACAN enabled and set to 11x in mission editor, yet turning on tacan and overlaying it on my HSI doesn't show Stennis on the HSI. Same with the ICLS, it doesn't work. 4. Again, no response from Stennis when I request inbound. Deck lights don't turn on either. This happens regardless of whether I set comm frequency via preset, or whether I do it manually. What am I doing wrong? All these thing (comms, TACAN, ICLS) work just fine on the Case 3 quick mission, but not when I setup my own mission. Please see attached screenshot for reference. Any help is appreciated. :helpsmilie:

Hi all, Thanks for the responses. Mate I turned up my textures to medium and cockpit displays resolution to 1024. This made a significant improvement, at the slight cost of SOMETIMES encountering a slight rendering delay when switching from exterior/chase view to cockpit view. Appreciate it mate. I'm actively flying only the F/A-18 and Su-33.

Hi all, With my i7, 2GB VRAM, and 16GB RAM, I'm able to get excellent framerates with overall setting = low, texture = medium, and anisotropic = 8x. Unsurprisingly, the frame rate shudders at medium/high settings, but I can live with the low settings. My question, is there a way to get higher quality resolution of the cockpit whilst in overall low settings, given that the cockpit stays relatively static compared to the ever changing terrain? It would be nice to see a crisp, photorealistic cockpit given that that makes up 50% of your view most of the time anyway. Cheers.

Mate this is simply excellent work. Professional grade! Thanks for all the time and hard work you undoubtedly put into this. I didn't read the entire thread, so forgive me if this has been answered, but I'm guessing that you will be updating the manual iteratively as ED releases module updates?

Thanks for the response man, but that didn't work. :cry: I think maybe this thread should be moved to the Su-33 forum? Mods please assist, cheers!

Hi guys, Previously, I had purchased Su-33 module and was running it on DCS World 2.5. I recently purchased and installed FC3. Now whilst I can still select and fly Su-33 via the 'Create Fast Mission' menu, I do not see Su-33 in the Instant Action menu anymore. The main issue with that is I cannot do carrier takeoffs anymore, since that was only available as a mission in instant action (Create Fast Mission doesn't have 'carrier' as a starting point, only ramp/runway/random). I checked module manager, and the Su-33 module is still installed and active. What gives? Cheers.

:cry:

Hi all. Joining the party late, didn't read all pages. Any ETA on this module? FWIW, Jane's F15 was my favourite sim ever. I'd kill for the F-15E on DCS :)

Hi guys, Forgive me I don't speak Italian. Hope I can ask my question in English. Any ETA on the release of the F-15 module? Grazie!

Yes!! You are exactly right mate. Reducing resolution to 1024 makes the buttons appear for proceeding to the next screen. However, I'm happy to report that I discovered DCS World 2.5 runs quite well on my PC, albeit in low settings. As such, I've graduated to FC3 on 2.5. Cheers!

Hi all, I have Flaming Cliffs 2, which I selected over DCS 1.5 because I can run it on max settings on my PC. I am only able to fly in Quick Start mode. There is nothing under the Training section. There are plenty of .miz missions under the Mission section, but when I double click them and the details appear, there is no way to proceed...no 'fly' or 'continue' button (actually no button at all). And all the campaigns show as 'Inactive'. What gives??? Please help :cry: