Zitat von »Falkenburger«

die zweite INIT Seite ist nicht verfügbar.

Zitat

und glauben alles was in irgendeinem Forum steht

Zitat von »RomanK«

[...] ein Produkt ohne VC möchte ich beispielsweise nicht haben.

Zitat von »guenseli«

Das Bug-O-Meter hat sich doch seit letztem Herbst nicht mehr bewegt, oder?

Zitat von »Nik Efimov«

Hello everyone,

I feel a good and honest situation report is well over-due, so let me fill everybody in as to what's happening at AirSimmer these days

First of all, we are all well, and work on the A320 project hasn't stopped in any way.

The release of the A320 Basic Edition was our first FS release as a team, so naturally it was the beginning of a steep learning curve for us. Thanks to the enormous efforts of our Customers, our Extended Team, as well as our internal Testing Team, we were able to understand exactly what we can do to improve our product further. With this, it became apparent that some fundamentals will need to be re-organized and re-designed.

Here are some of the technical decisions that we made that will improve the overall realism of the product:
1. The ultimate goal of our simulation software is to be able to provide professional-grade realism
2. More object-oriented approach in simulation. By this I mean coding hydraulic actuators, motors, valves, pumps, and so on as separate devices which will age, lose reliability with time, and have the ability to fail (although some functions will only be available in the Advanced Edition)
3. No-shortcuts approach. ELAC is a good example. For performance purposes, we did simplify the code for the ELAC computers. Now, we want to do it the real way - which will mean that both the COMMAND and MONITORING units of each ELAC will be running in parallel, cross-talking to each other, each of them having the ability to fail, glitch, etc to simulate malfunctions. This will mean that the ELAC software code will be run 4 times each cycle (1 time for command unit, 1 time for monitoring unit, for 2 ELAC computers). Sync option will be available to save performance and force MONITORING units to read the same as the COMMAND unit, and ELAC2 the same as ELAC1.

These changes will affect the most important systems first. Our plan is to totally finalize the Flight Control System first. After that, we will enhance the engine control system (engine, EIU, FADEC), and FMGS. Second-stage systems are fuel, wheel and braking, and air conditioning.

As scary as it might sound, I am very optimistic towards our makeover project. I am confident that we can spend our time very efficiently adding these new features. It was the core technology principles that took us the most time to develop (such as control loops, mathematical models, geometry calculations etc) and those will remain the same for the most part.

In the mean-time, we are workng hard on reducing CTDs and other technical problems that don't relate to aircraft systems.

Last but not least, I'd like to express our sincere appreciation of the support from the FS community that we have received over the last year - we would simply not exist without it!

I will bring back the culture of monthly updates - so you can expect the SITREPS in the beginning of each month.

Zitat

As scary as it might sound, I am very optimistic towards our makeover project

Zitat von » Nik Efimov«

Throughout the last month, we were working fully on the coming update for the Basic and ET versions. We focused on CTDs and major issues (FG behaviour, throttle axle problems, EFIS errors etc). We haven't finalized the final fix list as it can grow before the update is made public, which should happen before the next SITREP is published.

After this update is out, we will be focusing on what the previous SITREP was speaking about - the "Makeover".