PhoenixBvo

From that explanation I understand the seat has pitch rate damping. That is not attitude correction. The torque from the gyroscope is directly used to turn the rocket motor. This torque is proportional to angular rate and not to angle. It may seem like a minor detail, but it means that inverted attitude will NOT be corrected by the ACES II. It does hold its attitude and prevents tumbling. But you would be heading for the ground with the aircraft sink rate plus ejection seat velocity... Attitude correction would require a 6 degree of freedom inertial measurement unit plus correct initial alignment.

Well, then I hope they at least notice this issue (bump, bump, hint, hint :music_whistling:) and avoid it in A10C. Hopefully we'll have it fixed in the expected compatibility patch for Blackshark...

What makes you say they will not fix it? Do you mean that as a practical observation based on previous cases or that it isn't their duty? Because I believe that this is an important issue with so many users having high-end equipment with multiple monitors and DCS officially supporting Triplehead/Eyefinity... I would say this bug warrents a hotfix patch and ED/TFC owe it to their own high quality standards to do this... Please:(

Yep, exact same issue here. I use 1920x1080 on the main screen and 1280x1024 for the Shval. I get a stretched main viewport when turning on NVG, plus AA turns off. One additional effect: The NVG brightness is behaving different than before the patch. When I turn the power/brightness down, the NVG part of the screen fades to black instead of to the visual without NVG. Can anyone confirm this last observation? Should it be that way, i.e. do NVGs become opaque without power? I thought the technology it is based on is photo-amplifier tubes. Meaning the light is amplified, not recorded by a camera and then presented on a screen (which would yield the current behavior). Any thoughts? (Plus a fix would be really nice...)

Where did you get it????????!!!!!!!!!!! ME WANTS :joystick::joystick::joystick: I thought it wouldn't be available till at least september...

Perhaps its a graphics driver issue. Are you running on an ATI? I've had problems with some textures not appearing for certain AA settings (Adaptive Multi-Sample AA) in Catalyst 10.2 I'd suggest you try disabling AA/AF and any other custom settings to see if this brings the textures back...

Great data!! Thanks man. That's science, you should publish a paper on that :)

With both sides selected, you'll always be in the middle of the pattern because of the symmetry. I suspect that an IR missile will likely be programmed to aim for the centre of a hotspot. Therefore I always have a single wingtip selected. 0-1-6 for pre-emptive, just let it run as long as you're in the threat area and stop manually. 3-2-1 when I know where the threat is and I have eyes on him. I programmed the cougar to switch between the two modes with the press of a button :thumbup:

So you lack the muscle memory of a real pilot? That is the solution right there, what are we still talking about? :smilewink:

A dynamic campaign doesn't have to mean that an algorithm has to generate all mission elements. I imagine a good dynamic campaign engine still requires a lot of human input in the form of databases. For example, a variety of mappings of the terrain for mission variables such as ambush sites, terrain cover, possible axes of advance, suitable SAM locations, suitable supply routes, etc. The campaign engine would use all these databases in combination with the current military situation to decide where the elements in the next mission are located, how they move and so on. This should provide intelligent looking, yet ever varying missions, but it'd be a huge project to get it right...

Well, I can see the switches in that screenshot...

Maybe he meant distress? He makes a bit of a psychologically unstable impression...

This has been discussed before. A dev answered then that 100% is the estimated realistic probability. 0% would of course mean a birdless world. So it's basically a scaling factor for the probability. That's why 1000% could still leave your heli unstruck. The question is what the realistic probability at groundlevel is...

Uhm, I would say mostly teamspeak 3 nowadays...:)

This isn't "just" a game either :smilewink:. My guess is that the difficulty arises from the decision to make the sim easy-customisable. Because all settings and even some logic is stored in text format and option lists can be written in any order, it becomes very challenging to write an auto-merge tool for all .lua files. That is the price we pay for having so much freedom in fiddling around with every detail of the sim. I personally feel that's a small price...:thumbup:

They should do that when you get landing clearance...

One tip for people with a lot of changes in their 1.0.1 installation: Make use of a merge tool such as http://winmerge.org/ or better, but not freeware: Beyond Compare. This is what I did: Make a folder Backup at the level of your top blackshark folder; Move the whole installation to the Backup folder; Install the clean 1.0; Apply the 1.0.1 patch to this installation; Move this into something like "Compare"; Now do a folder compare (using the mergetool of your choice) on the clean 1.0.1 in Compare and your own edited version. You'll easily find all the changes which need to be applied to your final version; Now again do a clean 1.0 install; Apply patch 1.0.2; Apply the changes you found using the folder compare per file using Notepad++. Done! And you're sure you got everything without destroying the new settings.

correct :) Give em hell! :thumbup: Oh and perhaps a little tip: DO NOT rapidly reduce collective in such a situation. You might be tempted to do so when you see a smoke trail or tracers heading your way. The heli is very likely to enter a vortex ring state in that case. Instead disable autohover and apply sideways cyclic to slip away in any desired direction. You will then automatically loose some altitude which should be enough to drop behind the ridgeline again.

The collective break does not function completely as in reality. In the sim, it only has a function when alt hold is turned on. Then it temporarily disables the altitude holding mode to allow the pilot to make adjustments. When released the new altitude is set as reference value for the autopilot. The only (correct) way to change altitude in hover is to use collective. It doesn't matter whether you do this with altitude AP and collective break held or without altitude AP. As long as you remember to press the collective break when changing altitude with alt AP enabled otherwise the helicopter will fight your input with 20% control authority (meaning you can still change altitude, but with reduced effectiveness). Does that answer your question?

That's a map datum, not a coordinate system...:smartass: A map datum is usually an ellipsoid or similar 3D object which can be described by a geometric equation. This is then taken as the mean earth surface level (equivalent to MSL). WGS84 is an ellipsoid whos parameters have been taken to achieve an optimal fit on a global scale. There are numerous other map datums which have better local fits, but whos validity is limited to a certain area. In principle, any coordinate system can be chosen for a certain map datum. And then there is the map projection which is again a separate thing...

:huh: Are you talking about the insect? Cause an F-18 would have no problems with that speed.... In which case I'm wondering how you could have survived such a chase.

:thumbup: Cool! That looked like a walk in the park :music_whistling:. I have been too busy to try yet, but I'll try to copy that as soon as I can. For those max altitude attempts, I noticed your tanks were almost empty. Makes sense to carry as little as possible.

Well, I just got a medal awarded after a flight which I started from a track. The medal was also shown in the main menu. Not sure if any points or kills were recorded. But that feature seems very flaky anyway. Often I don't get kills even after campaign missions. Not that it's a big deal... But it got me thinkin' that maybe the campaign does accept missions resumed from a track, but that you'd have to: 1. not die in the part which you record as a track; 2 and resume before going back to the main menu. I'm going to try this...

Ok, so there we have a nice variation: Who can show a track/vid of a controlled landing on the summit of mount Elbrus? :) I'm at it!

I'll get two #3's as well. One will be laminated to hang it on my wall. Should be great for mission planning. The other of course for in-flight navigation. Can't wait!!!