JuiceMouse

If the intent is not to make the flight model closer to full fidelity, why change it at all? I do see how the translation from real-world pilot to simulation development is a bit more complicated than I think I can appreciate, though. I'm just seeing that the FM at the moment is, for all its relative complexity, falling back on the notion that making helicopters ultra-sensitive is the way to make them more realistic... which is just not so. It seems like RotorLib is pretty comprehensive. Is there any way we can get more detailed gauges such as torque, n1, n2?

After flying the humming bird and ghosthawk for a little bit, I gotta say im pretty disappointed. I will test further, but as it stands the way the FM handles basic helicopter aerodynamics, RPM and torque is wildly unrealistic. I don't want to be a negative nancy, here... but has anyone working on the FM actually flown a helicopter? Cause it doesnt seem like that is the case. Is there any way we can have a list of actual effects that will and will not be modeled? I hear ground effect IS modeled, but havent read that definitively anywhere. How about ETL, translational thrust, settling with power? How is the energy relationship between airspeed, altitude and rotor RPM modeled? How is engine power handled? If we're going to have a more complicated flight model, talking about it in terms of these more complicated things is going to be necessary... If you want my opinion, as a rated commercial helicopter pilot, on the 'flight experience' ... its nothing like flying a real helicopter.

As I have been with all stages of this dev, I'm quite impressed. Franze and Nod, you guys are doing a great job, my only complaint is that I cant fly this thing yet! As the IHADSS is the current focus, are there any plans for overlay of video from the tads/pnvs? Is that even possible? I suppose my desire for a DCS-level of fidelity is pretty lofty. As usual, if you have any questions regarding the system or the verbage seen in the symbology, just ask.

Looking great, Nod. I hope to enjoy flying these badboys around when I return from this sandy shit hole.

Sigh... these videos will download eventually. Yay for satellite internet in the middle of BFE.. I'm pretty stoked though. This is the most accurate I have ever seen a 64 in a game to date.

While the problems that people have expressed are valid, this would be an awesome addition. I realize that arma is primarily an infantry simulator, but the thing that I like most about it is the ambitious attempt to synergize men, ground vehicles and aircraft in as realistic a way as possible.. an improved flight model in general would be a badass addition for OA, a patch, or arma 3.

Is this a totally dead idea? I have seen scripts with fixable cameras for UAVs and the apaches to fire missiles.. but so far nothing that utilizes the gun. Chagrin =\

Thanks for the replies guys.. and the input I have tried it with SLI on/off in the Nvidia control panel only, but that didnt seem to have much affect at all on the crashes or the fps. Ive tried cpucount=4, I even tried cpucount=8 (because technically an i7 acts as 8 cores..), but that didnt really work either. I also tried -winxp, running in compatibility mode for xp sp2 and 3, and running as admin. Physically pulling out one of my 295s to truly try the SLI theory is not something I'm really willing to do, as with the 200 series I finally see SLI making a noticeable difference. Screwing around with the in-game settings does have an affect on my fps for sure, although if I reduce the settings enough to get a good frame rate (40ish), target ID at distance becomes pretty much impossible, and I may as well not be playing at all. I will re-try the SLI stuff more in depth, and screw around with my in-game settings some more.

UPDATE: I disabled SLI again today and tested it out. Flew around, shot people, was shot, etc. No crashes. Not sure why this didnt work before (drivers perhaps), but that seems to be my solution at the moment... fps is still trashy at best (25), however... but no crashes at least. Issue: Slightly inconsistent crashes, very consistent crappy fps. Video Settings: Visibility: 3600 Texture Detail: Normal Video Memory: High Antistropic Filtering: High Antialiasing: High Terrain Detail: Normal Object Detail: High Shadow Detail: High Post Process Effects: High Interface: Small Ratio: 16:10 Resolution: 1920x1200 (100%) Interface Res: 1920x1200 Relevant system specs: CPU: Intel Core I7 975 GPU: 2x EVGA Coop Nvidia GTX 295 RAM: 6GB DDR3 HDD: Seagate 1.5TB 7200rpm HHD / Intel X25M 80GB SSD OS: Windows 7 Ultimate 64bit Nvidia Drivers: 197.25, 197.15 Irrelevant(?) system specs: EVGA Mobo TrackIR 4 (Running TrackIR 5.0 software) Soundblaster X-FI Saitek Eclipse Keyboard Logitech G9 Cooler Master HAF 932 Things I have tried: Nvidia Control Panel Disable / Enable PhysX: Doesnt seem to be any affect either way, on either fps or crash frequency Force VSynch On/Off: Seems to increase fps in the opening carrier scene to 60-100ish (although my refresh rate is 60hz...).. but otherwise no affect Force Threading On/Off: No confirmed affect Multi-Display setting to Single: No confirmed affect Anti-Aliasing Low/High/On/Off: No confirmed affect Triple Buffering forced on/off: No confirmed affect Overclocking GPU (have NOT tried underclocking): No affect SLI on/off: Disabling SLI seems to work now.. [*]SSD/HHD: No affect on crashes either way, small improvement in performance on the SSD. [*]Antivirus on/off, AVG/Antivir: No confirmed affect [*]TrackIR on/off: No confirmed affect (Although if I cant use TrackIR, playing would be pointless for me) [*]Drivers: Other than screwing up Battlefield2 a bit MORE, no affect. [*]Mods: ACE2/Vanilla.. doesnt seem to matter [*]Windows compatibility: -winxp, -cpucount=4, compatibility mode for xp, vista, run as admin etc: No confirmed affect Further reading: Been testing on Domi for the most part. On the airfield I get about 25fps at best, which would be acceptable, if not for drops to 10-15 if I turn my head, and crashes that seem to happen just whenever. I originally thought they were time-based.. but sometimes it crashes on the Domi zoom-in. I thought it was based on flying somehow, and that does seem to exacerbate the problem but eventually performance suffers and textures start tearing and artifacting. Based on that I thought it might be heat-based, but monitoring my GPU temps reveals they operate at about the same levels as when im playing any other game. Other GPU-intensive applications (BFBC2 on super-max settings, Left4Dead2 maxed, 3 clients of Eve Online maxed, Borderlands maxed, Dragon Age maxed...) have little or no issues at all. At any rate, I loved the original OpFP, but it was buggy and crashy.. liked ArmA, but it was buggy and crashy, LOVE ArmA2... but Its BUGGY AND CRASHY. I guess the timing of my systems over the years has put me too far infront or too far behind these fantastic, tragic, games.. If anyone can help me out, has any ideas or suggestions, or has something that has worked for them with similar specs (even if I have tried it), please let me know...