Allesmor Obranna

Su-27 with R-77, double S-25 launcher and MER*6 FAB-250s

In the good old days, in early 60's, in the Hungarian Air Force, the altitude 22000-23000 meter was quite normal with the MiG-21F-13. After it, with the MiG-21PF, the flight altitude above 20000 meter was still a daily routine, however, in the 70's, the normal practice has year by year more low level aerobatic, instead of the high altitude intercept. The PF was the last MiG-21 type in the HuAF which was used more on high altitude than lower. Even if it was one of the best aerobatic capability model by its very clean airframe and a little bit more powerful engine. With the MiG-21MF, the so called "Razgon" mission was only until 18000 meter, maybe up to 19000. From the second half of the 70's when the first group of MiG-21bis started the service here, the max altitude decreased to 16000 meter, since on this flight level the risk of the engine stall was moderate. As far as I know, the highest hungarian flight altitude with the MiG-21bis was 19800 meter, on a post-overhaul test flight, in May, 1988. During this flight the engine was stopped, while the restart process had some difficulties. I don't know any other case when a HuAF MiG-21bis was higher than this altitude.

Have you ever heard this bang in a real life? I mean, from an F-15C? I mean from a PW220 engine. It is not so typical. I have herd at once in lakenheathy, it was a big surprise too, but no any other C or D model produced similar before or after. And of course the E model's PW229 engines which have a 11 stages AB ignition is also did not provide a bang. This kind of sudden noise step up is typical for the MiG-21 family, where the nozzle is operated by the main hydraulic system and opened first before the ignition occured, to avoid the engine stall. Thats why the afterburner chamber fills a little bit dense mixture of fuel and started with a big bang. It is a trademark of all kind of MiG-21 engines, like the R-11, R-13 or the R-25. Check these videos: or It is not a "bang" sound like in the DCS, it is a sudden sound increasion. Same has the Su-22M4's and Su-24's AL-21F3 engines, where the AB has also a very hard noise level up. The AL-31F family also sounds like these engines during the take off, but in flight, these kind of staged sound difference during the AB ignition is not typical. The normal F-15C AB ignition sound is like this one: Very powerful, but there is no any explosion-like big bang. Thats why I think it is not ok in the current F-15 model.

This bang sound when we ignite the afterburner quite annoying, it is ok for a MiG-21, for a Su-22M4, or even for an F-106, but for an F-15?! The F-100PW100 had a hard AB ignition issue back in the good old days at the beginning, but the 220 series... not really. I heard it only at once in Lakenheath, only one single plane did that at take off, only one F-15C, that was amazing, but it is not typical. However, in the DCS, every time when I lit on the burner, it sounds like a nuke attack... :) This is what I really looking for:

Just a quick nostalgia I found my notes from an argue back in 2003, when the Lock On was a part of the Ubisoft Forum. At that time my nickname was kolbola and I talked about that the cockpit was not a real 3D, despite what the IL-2 had. As I read back the text it seems that my communication performance was not so... accurate? Let say, it was totally wrong, even if what I said was true. I was just frustrated... sorry. Funny thing that the final consequence is at the bottom of the flame: -who cares the 3D cockpit since we have a serious simulator?! :))) I glad to see how far we are now from those days. (sidenote: My first meeting with this saga was in ~1996, DOS based Flanker 1.0 or 1.1 and I was a very big fan of it...) http://forums.ubi.com/archive/index.php/t-21085.html

+1

OK I re-check the issue. It is happengin every time, when I use the embarking options for an infantry team. If a waypoint contains the embarking order, the waypoint is fixed to the map. This issue is detected only after the 1.5.4. The previous had no this one, every waypoint remained moveable, even if it had an embarking option.

Mi-8, Mi-24, Ka-50... I checked all of my missions from the latest 1.5.3 edition. Under the 1.5.4, all previous waypoints are fixed to the map, all new (re-edited under 1.5.4) also. In a new mission, started under 1.5.4, the waypoint issue also occured.

If you put down a waypoint, then it fixed to the map, unable to move as earlier.

Yes, the engine of the Google Earth has a full 3D, phototexturized and real time shadowed objects, generated from the satellite image by the early version of the Deep Stereo algorythm.

+1, yes these trees seems to be too cartoonish related to the higher resolution of the ground texture. And all of them are just the same tree shape cloned. So it is ok, but it is far from for example google 3D flight simulator which is also very simple, but looks more real.

Thanks for the info.

I opened an issue in the Leatherneck bug tracker about this, since all of Watch Track option is failed. If you did a normal demo flight above an airfiled, when you watch it back, the plane retract its gear on the ground or after a few seconds automatickly fall from the sky. If you add an AI, who shoot you down during a few minutes dogfight, in the reply it kills you right from the start. Somehow the track playback is always shows a crash, an off-runway accident or any other event which was not happaned.

+1

Ok the reason behind my game crash is revealed, the Nvidia 364.72 driver update was the rootcause, since this driver has a very serious bug. Almost every Nvidia card user, who updated his driver to this one, may be lost his entire OS as I experienced. Maybe the Win10 users are in safe.

I have the latest nvidia driver, but I updated it up after the first game crash occured. This nvwgf2umx.dll thing has a lot of problem, as I the google checked.

updated with open beta's log Logs open beta.zip

Attached. Thanks Logs.zip

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-04-15T20:57:04.000000000Z" /> <EventRecordID>146079</EventRecordID> <Channel>Application</Channel> <Computer>x-PC</Computer> <Security /> </System> - <EventData> <Data>DCS.exe</Data> <Data>1.5.3.52018</Data> <Data>5706392d</Data> <Data>nvwgf2umx.dll</Data> <Data>10.18.13.6472</Data> <Data>56f0a450</Data> <Data>c0000005</Data> <Data>0000000000958ee6</Data> <Data>1b60</Data> <Data>01d1975840762451</Data> <Data>C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe</Data> <Data>C:\Windows\system32\nvwgf2umx.dll</Data> <Data>9af5aaac-034c-11e6-936c-902b341dbc50</Data> </EventData> </Event> Here is what I was able to get out yet, more to come

Problem signature: Problem Event Name: APPCRASH Application Name: DCS.exe Application Version: 1.5.3.52018 Application timestamp: 5706392d Fault Modul Name: nvwgf2umx.dll Fault Modul version: 10.18.13.6472 Fault Modul timestamp: 56f0a450 Exception Code: c0000005 Exception Offset: 0000000000958ee6 Operation System version: 6.1.7601.2.1.0.256.1 Locale ID: 1038 Additional Information 1: c58c Additional Information 2: c58ce741126a77333aa32253d9d6b6a2 Additional Information 3: b515 Additional Information 4: b5153bcf872487878898f18a28a751c4 I have under the Mi-8 module an error, happened every time, after the exactly same time of operating. Complete game crash. The issue is came only with the latest upgrade. Not happened earlier, or under a different module, with this upgrade.

Exactly similar issue here. DCS (especially the Mi-8 module) is stopped after a few minutes flying. The whole game is crashed. Not happened earlyer, only since the last update.

This afterburner shape form 1.5 does so good as was it until the previous version (except the color). These rings are incorrect, I tried to create a better one, but the 1.5 file system did not allow it. :(

With the F11 you can go down really to the ground level.

Check the nearest airport, click on it under the map view(F10) and you can "fly" to anywhere where you want to put your viewpoint in F11. Then you turn your camera to your plane (best if you put your position on the ground and watching to the sky) and push the ( NUM, ) which a padlock to your plane. Just start your airshow at an airport. in this case you can stay there and easily do what I wrote above... PS: if you crash during your flight, the padlock camera immediatelly turn back to the beginning position where locked your plane first. To prevent this, you can follow the show by your hand via mouse. [ame] [/ame] PS2: the module MiG-21bis under 1.5.3 is wrong, because it is doing something totally different than what you did before. Mostly retract the gears during the takeoff on the ground or just miss a turn and hit the ground a few seconds later. I don't know why. It is a bug.

I really need the whole pack of HuAF skins. It is very highly extremely important for me! :)