Luzifer

Nope, everything is correct. http://forums.eagle.ru/showthread.php?t=105074&highlight=gauge

The DCS folder with all the configuration should be in the "Saved Games" folder in your user directory.

Of course the exact same thing can be said about most boys. DCS doesn't really compete with first person shooter blockbusters when it comes to popularity…

Not to mention millions of uncalibrated photographs with endless variations of film/sensor spectral sensitivity, different white balance settings and not the least manual or automated image processing to make it "look good". It's an art to make your graphics look good and/or natural (more specifically, to make it be perceived as "natural"). I'm always a bit amused at the suggestion that to make the colours "realistic" you just have to take a photograph and pick the colors out of it. :doh: Also, didn't the devs mention once that they go for the hyperrealism style in graphics?

Certainly not worldwide, Russia (and China?) being the most notable exception, as well as smaller niches such as gliders in Germany which are still fully metric. Of course, the point still stands for the A-10, which isn't operated with metric units anywhere. Just like you wouldn't want to operate a Russian aircraft in imperial, it just clashes with all the existing documentation elsewhere.

Of course it will "look through" the target, it can't take the target into account simply from the optical image. It takes the planes location and orientation as well as the direction the sensor is pointing and computes the location of the SPI as the point where line of sight intersects with the ground (according to a detailed terrain elevation map). The shallower the angle and the higher above the ground you target, the more pronounced the effect. As soon as you use the laser, it will combine the range measurement from the laser with the position and line of sight data to compute the correct SPI location above ground.

When locked in normal mode the lines of the cross should go to the edges of the object it locked on. So how big the gaps are depends on how big the object appears on the screen.

That's gonna be the flashiest Baghdad of all time.

Nope, I have a Radeon and I see this issue.

Watch the g meter and pull. That should give you an idea how much pulling is pulling too hard. Of course in real life, you would immediately and very much feel that you're pulling six gees so you would be less prone to accidental stalling.

I've stumbled over that too - it will tell you "INS NAV READY" before alignment is complete and you can switch to degraded NAV which will not allow EAC to activate (it will continue alignment and EAC will be available later). "INS NAV READY" will be flashing when it's really good to go.

Davon habe ich im englischen Teil des Forums schon gelesen, ist ein Bug von 1.2.6. Möglicherweise eine fehlende Textur. http://forums.eagle.ru/showthread.php?t=113404

There are limits on the temperature? Well there's no english manual yet so I wouldn't know. :music_whistling: This was just for demonstration purposes anyway.

I don't know. I can go 280 km/h at sea level without shaking and without full collective. Autopilot active except for altitude hold.

No? I usually find myself at 250 km/h very quickly if I don't pay attention to my speed and I am not even close to using full collective. I was mostly flying on multiplayer servers where the provided helos aren't fueled up to the gills though. It's faster than the Huey in any case.

It wouldn't make any sense otherwise. Max speed is given in true air speed and the relation between indicated and true air speed depends on air pressure. Air pressure depends on altitude above sea level, ground elevation doesn't come into it.

As it stands now, it really can't. According to ED, the old Nevada map that was in the A-10C beta has been canned years ago, the new one is built for EDGE.

A better format could be modeled on video compression. Most motion compression consist of building a frame by modifying previous frames (move that block of pixels from there to there, change a couple of pixels there) and so has the same dependency on previous frames. That has the same potential problems, i.e. errors propagate forward and amplify, no seekability. The solution there is that regularly full frames without interdependencies are inserted, which limit error buildup and allow skipping to those frames. Something similar could be done for a track format, i.e. every few seconds a full state is saved for the same benefits. This would limit drift to at most that which can accumulate in the time span between full states and allow skipping forward and backward.

I'm pretty sure Il-2 tracks worked the same way, as do other games. There is a good reason for that which does not involve training systems: track files are small and require little resources to create while running the game. Additionally track replay does not need special code, just running the normal simulation with the track file providing input in place of the user. If the simulation is fully deterministic, this will work fine. In practice, if the simulation is not very carefully coded for just this purpose. numerical instabilities will cause large deviations. Even if it worked perfectly, you still couldn't rewind (simulation can't run backwards) or skip forward (everything between now and the later position needs to be fully simulated).

According to the devs, such a campaign is in the works, even by the same author as the UH-1H UN campaign.

Now if only the Ka-50 would also work like that…

So one B-17 dropped their bombs through another B-17's elevator? That's… that's kind of a dick move right there.

And what does Belsimtek have to do with ED's development of the F-18C?

Bug, I think. In multiplayer I can see the effect only on other Hueys but never my own. In the Mi-8 on the other hand, it works fine.

Got sniped, I was just gonna post the xkcd link...