last1976

? ? I attached whole log folder above in first post. My specs in this case are: [AMD Phenom II X4 965 BE @3.6GHZ, 660GTX 2GB, 8GB DDR2, Windows 10 Pro]

Again I crashed after 10 min, with same errors as above. What I see is that after some time there is a bigger stutter, after that the ram usage of dcs process is cut too half from little under 3GB to 1,2GB to 1.5 GB. As you stated in Changelog you fixed a Memory leak, wich by the way I never had. As posted above until this patch I have not had one single crash. You guys are sure you fixed? The behavior right know appears somehow like you ve "fixed" it with some quirky dirty script, wich flushes ram somehow. As I read the last opened threads in this forum a lot of guys are getting the same crashes.

So is there any clue, whats wrong ? Is it OOM ?

Since release of open beta 1.5 I have not had one single Crash. Since last patch I am barely able to play through any mission without a crash "Dcs have stopped working". Logs.rar

Hi, Dcs is constantly crashing, at the moment I deploy rockets on the guys sitting on the rooftop attacking Ford.

same here. As its not a big hit I definitely got a overall hit on different missions with different modules of a stable 80 to 90 fps to 60 to 70

Its all good. I am concentrating on the other side of the medal. The download is so slow, I can easily stream on 4k in the meantime. This wasnt possible untill now. So a step forward was made. Thanks Gesendet von meinem GT-I9300 mit Tapatalk

I think everybody understood the issues on release, including me. But coming home from work, with the intent to some flight time, seeing "Oh there s a new update, nice" just to be confronted with the fact a small 1.2 GB, wich has been downloaded in minutes for years now without any issues, is now downloaded with 6 kb/ s for what "reasons", I tend to assume its for saving up traffic?. That is just slightly annoying. And I m trying to be kind.

The object of interest for me is, will the tree blending soon (1 to 2 days) fixed in a hotfix, or will it only come with the next patch. If first I will wait because it is really distracting for me, if second I will try too revert to earlier version, because I cant wait that long .).

As the graphics in a whole are somehow corrupted in the latest patch, for example object blending etc. I would recommend you guys waiting on the hotfix and the results will be more representative.

And again flown the mission. There are definetly no troops in the village. I found some guys around a btr outside the village, but nothing happens if I land next to them. I think this mission is broken in 1.5, would be nice if someone using 1.5 could confirm or deny.

The problem is. After destroying the jeep nothing happens anymore. No message, no smoke, no infantry on ground nothing.

Ok i found the jeep. You maybe could tell wich buildings you hit because i hit a lot of them but no ongoiing mission after destroying jeep. Gesendet von meinem GT-I9300 mit Tapatalk

It seems the trigger is broken for that in beta, the message comes and there is definitely not any vehicle moving out of the village. By the way even if working, the screenplay of the mission is more than questionable. How is the outpost from its position to see there is something moving out of the village. And in the Message the village is suddenly called a town. So if you listen more closely you get more confused, what should not be the case.

I even cant find the enemy vehicle how am I suposed to know from wich town it is trying to escape? Gesendet von meinem GT-I9300 mit Tapatalk

Wasn´t it stated that 1.5 will get a common Ui for both SP and MP. I this is correct it seem logical for me the mp icon is no more working and the right way to go MP is the UI. Correct me if i´m wrong

Dear ED Staff, im in the sim since lockon. I ve gone through a lot of tweaks, patches and bought a lot of cpu´s and gpu´s but this time, from what i´ve seen so far. You guys really done it finally. This engine rocks so hard, I m getting double fps or even more on very very nice looking screens. Congrats you ve done such an amazing job on the engine. Durchschuss

This is so amazing!

Now as half a year has gone. Its seems still to be broken. ED is aware of this ?

@ yo-yo I testet last night. For me it seems to be case II as i am getting the biggest deflection at 100% Joystick. It doesnt seem to be limited on input side. Assumed that is correct . I really recommend same corresponding limitations on Input as on Output Side to maintain linear Feedback. As there are few to nobody customer who has Access to real force feedback devices we really are depending on synced in and output.

You dont think to the end. case 1 means i can figure out if im pulling beyond the planes limit If I stop there nothing bad will happen if the plane is slowing down. Case two will lead to oversteering without any stick movement when plane gets slower.

I really hope it s case 1, no clue how you could prefer case 2. Case 2 would be a game stopper for me. Case one would be provide much more control.

As discussed wildly in our teamspeak without result. My Question is. Assumed max ingame stick deflection would be 30% degree at 500 kph. Is it implemented like Case 1: 30% joystick movement => 30% ingame stick movement further moving joystick cuted off ? or is it Case 2: 100% joystick movement => 30% ingame stick 30% joystick movement => 9% ingame stick ? Many thanks Durchschuss

As your tone is arrogant and offensive, I suggest you shift your coarse manners. If you managed it I maybe consider to take advice from you. Yours Sincerely

Well to be honest I couldn't reproduce it that way either.:music_whistling: The Vrs exists at about 1500fpm - 2000fpm ? Maybe it is just easier to recover. When I hold the heli exactly in position it wont recover from higher descent rates. So well, I acknowledge that under this conditions this thread is becoming unnecessary as my experience is not that great, that i would claim this is realistic or not. Maybe it is. At the time I opened the thread I had a situation where it seemed the VRS is not implemented anymore. I think opening this thread was an act of precipitation