ZaltysZ

Maybe they are for arcade mode?

Probably it is too early to give a rating, but that feature list looks like a very good product is coming. I am not huge fan of A10, so plane itself does not impress me much (so far), but those improvements of DCS engine do. Some of them will probable be a way bigger advancement, than DCS: Ka-50 was over FC. :pilotfly:

Write the error message down and post it here. There is great possibility, that you are getting usual issues, when game is installed into Program Files. If so, install it to different location.

Rotor mass plays its role. You need to be quicker with collective if your helicopter has light rotor.

I am maneuvering holding the trim from the beginning I got this sim, because it is the only "stable" way while using non FFB controllers. It never happened to me, that rudder has stuck to side or something like that.

In 2 years I haven't experienced anything like that. :huh:

Red box does not show position of rudder (control surface), but it shows position of pedals (control device). Keep in mind that it does only show position of virtual controls (in game collective, cyclic, pedals), but not position of your game controllers (i.e. joysticks). I.e., if right pedal is pressed fully in game, red box will show pedals mark fully to right. I suspect that you and AP may still not live in peace. Remember, that AI has 20% authority and if it is told to do something, it may wrestle you by using those 20%. Pedals might be centered, by aircraft might still turn around, just because AP makes it do so. AP does not move your controls, so red box won't help you tracking what AP does.

You must break trim button effect into 2 parts: force trim and AP commands. Force trim always works on all 3 axis and is not affected by which AP mode is chosen. However, commands sent by trim button to AP do depend on AP mode. In hover mode, trim button designates new hover point and direction. In route mode it designates speed and direction (if no waypoint is chosen). Pedals position is shown under red box.

1.0.2 gave us new sound engine, with which game should exploit multiple CPUs even on XP.

With immortality you just bounce when you hit ground hard enough for a crash. Turn that off. :smilewink: P.S.: really, turn immortality off even while learning or you will risk getting bad habits whose will later punish you with rotor blade collisions.

"Reset trim" will always (with 0 wind) result in aircraft drifting backwards. This is because "reset trim" puts controls into default positon, which is position for compensating helo tendency to roll forward while it is standing on the ground. In other words "reset trim" trims your aircraft for parking, not for hovering. Trim button not only affects trim, but also gives commands to stabilization system. While hover mode is on, trim button sets new hovering point. AP needs time and effort to bring helo to designated hovering point. With every trim button press, you basically tell AP: "Forget that hover point, which are far away already; lets hover where we are now". Carrying this multiple times will make AP slow the drift to zero. In contrast, if you have designated hover point only once, AP will need not only to kill the drift which is present at the moment of hover point designation, but it will also need to drift back to that point. With not enough small drift, this may take too long or even totally fail, so it is better to hit trim button multiple times and kill the drift this way. P.S: "Reset trim" is optional game feature. Real Ka-50 does not have such thing as "reset trim".

He is just frustrated a little bit. :)

Where did you get that line? DxDiag? If so, "English Final Debug"indicates that you are using DirectX for developers (debug version). It is slower than "Final Retail" and might take its part in your low FPS problem.

Red box only shows where your controls are, it does not show where your controls should be for hover. You can't know if controls are within 20% zone just from red box, because this zone is not absolute, it is relative and depends on your aircraft attitude and forces (like wind) acting on your helo. The only way to know if controls are within that zone, is to know exactly where controls should be for hover, but if you are constantly drifting, you obviously don't know where they should be (don't worry, most of us don't know in advance). You need to trim helo so that there was no vector line on hud, and only then engage the hover mode. Hover mode is not supposed to remove the drift, it is supposed to prevent the drift (this is not word play, it is important). If you can't get rid of tiny vector line, hit trim button a few times after engaging hover mode - it should settle the helo.

http://www.ipix.lt/images/59897578.jpg :music_whistling:

It is like parking brake in car. You first need to stop and only then engage it. :smartass:

Yes, of course. But "passable" is very subjective word. :D

In fact, it is normal. I know lots of people who had the same problem in first weeks they started using head tracking. Try remembering the first time you have used the joystick: strained hand, sweat all over the place, but after some time it became very easy and transparent. The same is with head tracking - body needs to get used to new tricks. :D

For authors: Little note for upcoming missions. Maybe it would be good idea to put voice messages before turning points of AI. Something like: "Soon we will turn left" and so on. AI never cares what is flying next to him and it would be nice to know about its "break" turns in advance. Now it is like driving behind a drunkard car, constantly on watch for accident. :pilotfly: For players: Make notes or learn the briefing map. Some areas have names, whose you won't find in ABRIS or F10 map. You need to know them, because they are sometimes used in radio messages.

Visible light isn't a problem, but heat sources are. You can check what your TrackIR sees in software (Camera view). If it sees more than 3 dots, you have unwanted IR source. You can use the same Camera view to check how reflectors are seen at different angles of your head. If at certain angle TrackIR sees less than 3 dots, it looses tracking, so you need to adjust position and distance of TrackIR unit or position of your cap. Ultimately, you can try making your own reflector set by using some small balls wrapped in reflective tape. Original reflector set has disadvantage, because it has reflective area only at front and it can't reflect much once you turn your head away.

1) If you destroy ME coordinates for SP mission, pre flight planer will show weird plan. 2) If you have ME coordinates destroyed, but coordinates of game engine are ok, you can recalculate coordinates for ME. Simple utility doing this automatically will destroy this as mean of protection.

Now, tell me if there is a way to fix 3D cockpits in F4 AF :) I mean those damn gauges.

So, are we there yet? :)

They made the speech dependent on country you select. If your helo belongs to NATO forces, you will get English speech.

Your impression is correct. Auto sequence in ABRIS means that next waypoint (in ABRIS only) is chosen automatically when you get close enough to the current waypoint. Seems the same to me, unless we are talking about the case with cockpit illumination on. There is a bug, which prevents PVI buttons to illuminate when cockpit illumination is on, however they still function as intended. --- It would be better if you recorded a track and attached it here. It would be easier to identify a problem.