sobek

http://forums.eagle.ru/showthread.php?t=147710

Hardware, GPU driver, operating system, etc.?

http://forums.eagle.ru/showthread.php?t=147740

Restart windows and try again. Don't start DCS or the regular updater before you run the OB updater.

Well actually since the introduction of the patch system, it shouldn't be a problem.

You need to install Visual C++ runtimes.

There's a separate installer for open beta installs.

Ich meinte das packen von Installern.

Das macht ihr aber vermutlich nicht für jeden Build. Auch dieser Prozess kann schieflaufen. Ich versteh trotzdem noch nicht, wie du darauf schließen willst, dass ED keine automatisierten Builds fahren?

Natürlich haben die einen Build Server. Das tut aber nichts zur Sache. Der Build Server kann deinen RC 10x fehlerfrei kompilieren, davon hast du aber nichts, wenn beim Packen des Installers was in die Hose geht.

The updater is a program that checks whether your installation matches with the "repository", that is, a remote "installation folder" on the server, it works pretty much like versioning software (in fact its functionality comes pretty close in some regards). The things that don't match are made to match. Voilá. There's nothing 'magic' about core changes so that you can't make an update out of them by replacing the respective files with the new ones, deleting those that become obsolete and creating those that are new. When all the assets change around a lot (lots of new code, a lot of new data like textures etc.) the return for patching diminishes, that is, you don't save a lot of transfer volume by keeping the stuff that did not change, but it can be done this way nonetheless.

This is exactly what i was getting at. Fuel measurement inside vehicles is done based on fill level, not some weighing measurement technique.

It sounds like the cookie is only being accepted for the session and discarded afterwards.

And how is this accomplished, inside an airplane?

Consider yourself corrected. :) It will most likely be installed through the autoupdater just like any other update.

You can tell the autoupdater to update your install to open beta. Otherwise you will be excluded from the beta phase.

It was a bit in limbo, pending a decision whether the bugs currently present necessitate a delay or not.

If you subject the plane to negative g for a period longer than a few seconds, the fuel lines will run dry and the engines will starve.

It's always a function of wing load, with the addition of centrifugal force in helicopters.

Please state the difference.

Das war schon immer so. Der Hotas (Hardware oder zumindest der Treiber) überträgt bei Schaltern nur Deltas, daher muss ein Delta auf die richtige Position kommen bevor die Synchronisation hergestellt ist und die Simulation auf die Befehle reagiert. Am Bsp. des Idle Detent Schalters: Wenn der Schalter bei Simulationsstart in der OFF Position ist, herrscht zwar prinzipiell Synchronisation, doch die Simulation weiß nichts davon. Sichergestellt ist dies erst, wenn dann tatsächlich der Übergang von IDLE auf OFF übertragen wird.

Ka-50 has it, Mi-8 has it, not sure about the Huey.

Vorsicht:

Well for one thing, it puts a lot of additional work on the hands of the testers that need to sieve through possibly already reported bugs. Then as i said, if the devs are task saturated, they won't start fixing bugs faster just because there's more people fixing them. In the end, this is all highly hypothetical, it's up to ED to decide in what state and when they want to release an open beta.

Why not? When 1.5 is released, people will still find bugs, most likely more than should be in a release version. All the while, people who want a stable version can stay on 1.2.xx