FSKRipper

Ich habe mal gerade auf die Schnelle etwas Munition verblasen, mein Fazit wäre das die Genauigkeit noch immer etwas befremdlich wirkt. Ein T-72 Kill ist allerdings ohne Weiteres möglich. Da ich nicht weiß ob der Track vernünftig wiedergegeben wird hier die Kurzfassung: Angriff von hinten/oben: Dürfte dank des Hitpoint Modells und der schwachen Panzerung den meisten Schaden verursacht haben. Bitte bedenken: Es gibt für das Fahrzeug trotz Rauch keinen Unterschied zwischen 100% Einsatzfähig und 1% Einsatzfähig... Angriff tief/von der Seite: eigentlich weniger Chance auf Erfolg aber dank des Vorschadens ein sofortiger Kill. :pilotfly: Meine Angriffe erfolgten nach 2 Gläsern Wein und ohne jegliches Standardverfahren. Aber selbst so dürften mit einem vollen Magazin etwa 4-6 Kills kein Problem sein. :pilotfly: Anmerkung: Wie bereits weiter oben erwähnt wurde zählen bei der A-10 eigentlich die "mission kills", also die Panzer die wegen Motor/Getriebe/Laufrollenschaden bzw. anderen Schäden (Bewaffnung, Optiken etc.) ausfallen. Dieses Detail ist in DCS allerdings noch nicht simuliert. Da ED aber bereits fleißig Informationen sammelt, dürfte ein DCS:M1 Abrams nicht mehr allzu viele Jahre entfernt sein :) Gun.trk

Hey guys, as the title say I encountered framerate issues with activated cockpit mirrors. The fps will sink by ~17 no matter if on ground or airborne and no matter if the mirrors are in my field of view or not. Test Mission for ground: Kobuleti ramp start (custom mission) Test Mission for Air: FC3: F-15C Instant Action Intercept DCS Version 1.5.0.45655 System.nfo here at first post: http://forums.eagle.ru/showthread.php?p=2493935#post2493935 EDIT: I reported this because several people I contacted experienced no significant loss in fps at all.

Bei mir läuft es eigentlich auch super allerdings kann ich das mit den Spiegeln so nicht unterschreiben. Eine Mission mit einer A-10 oder F-15C auf Kobuleti im Kaltstart erstellt und die aktivierten Spiegel ziehen 20fps von der (immernoch guten, >60fps) Gesamtperformance. Werde heute nach Feierabend auch einen Bugreport schreiben da das bei mir erst nach dem Hotfix 2 auftrat.

As there are some problems with navigation I would vote for a gunsight or bombing tutorial :music_whistling:

+1 Never experienced this in our clubs RG172 and on my motorbike at levels compareable to modern video games. The only feature that would fit is a kind of tunnel effect like under high G-load.

As the title said, with todays hotfix 2, I'm no longer able to use move the cockpit camera foward or back. This happens for default settings and remapped keys as well. I'm using a vanilla install, other commands (Cockpit camera up/down f.e.) work for me. Tested modules so far: L-39, KA-50 and MiG-21 EDIT: Did a second repair, the updater downloaded 141MB and everything works fine now. Thread could be deleted.

Thanks for your work. Nice bombing runs. As you said the G-Load was a bit much but I have seen what I was interested in... First of all the pipper started to move, thats a correct statement and I can not finally judge on this. It will take some time for me to do some tests on the weekend but the intersting thing happened during your last bombing run in the video. You pickled the second bomb after the pipper has moved above the target, to be exact the target is nearly at the outer ring of the pipper but you bombs are hitting in front/direct at the target. My assumptions would be in descending order 1. Your bombs hit the target because of your steep and fast dive to the target. Even with a completely fixed gunsight the bombs would have been near or on the tanks. Thats the way it was done before the little electronic toys came out. 2. In fact there is still some kind of CCIP integrated

Sure it isn't this? http://forums.eagle.ru/showpost.php?p=2510887&postcount=7

You are very much experimenting with your settings in different reports (looking at the ground there seems to be no or very low AA or AF in your current screenshots?). Could you post a complete picture of your ingame and CCC settings for this bug report as well as a notice if you are running crossfire or single GPU? If Crossfire is enabled you will know that there are several issues..

First of all this is a bug report forum so this thread is wrong in this place and will be moved shortly. To give you a hint, get a very good GPU and a medium/upper level CPU, this will bring your DCS experience to a new level.

Sorry but I can't judge anything from your pictures. Could you post the complete Tacview file or a DCS trackfile? BTW: Some reliable sources said that at least early heat seeking missiles can lock the sun in this version...

I'm aware that the ASP-3NMU is a different gunsight but according to ED's manual of the L-39 bombing is conducted with the sight in "fixed" mode instead of "gyro".

This would perfectly match with my findings one post above. Use a very steep angle and it's more like WW2 bombing :)

Ok, would be really nice to see an illuminative track from you guys, maybe this will teach me the way you do it. I tried to reproduce it but the only way was with a really hard dive bomb of 60 degrees where my bombs hit the target at the point where the pipper was during release. Thats near the point the Stukas used without any electronics. Edit: I started my dive at 3000m and dropped at 1500m without a moving pipper. I have for sure not enough routine on the 21 but I it seems difficult to make a safe recover under 5G when dropping later.

Could you be so kind to upload a track when you had the time for additional tests?

Nope, I asked because it sounded to me that you were refering to him while he posted he used simple ASP settings.

Have you tried it yourself or are you refering to kobymarus post?

Test was performed with the MiG-21 instant Action cold start. Looking left after mission start (where the other planes are) will put enough stress to the system :lol: My findings so far: Nvidia adaptive VSync on / VSync in game options off = ingame counter still shows ~80fps (seems to be fixed when switching to real Fullscreen by alt + return -> smooth gameplay) Nvidia adaptive VSync on / VSync in game options on = ingame counter locked to 60 fps and smooth gameplay Nvidia adaptive VSync on / VSync in game options off + Framelock 60 in the graphics.lua = counter shows 54-60 fps, noticable tearing effects (I know that is a very subjective point of view) Overall the switching to real fullscreen isn't really noticable in fps on my system except for applying the Nvidia settings without ingame VSync. For every change of ingame VSync you have to restart DCS to make it work. I really thought the Nvidia settings would overwrite the ingame Settings, even in windowed mode...

Nope, not possible and also not planned afaik.

Could one of you guys post a trackfile, your System specs and mission name? Would save a huge amount of time for the developers and other testers to replicate it!

I reported it not because my game stutters, it's running fine with 70fps with DoF enabled but the performance breakdown is quite a number and should in this case be pointed out as bonus option for our cinema enthusiasts and a red warning with capital letters for the common player :music_whistling:

Checked the other threads. Memory leak seems to be mostly a MP issue. When this appeared the game crashed in most cases. Did you experienced the same behaviour? I ask because at this point you are the only tester experiencing such dramatic fps issues. BTW I know that we are talking about a beta but that does not always mean that the issue is on the software side...Have you tried a single GPU setup? Edit: I watched your video again and again in 1080p. Your fps were never in a region of 120, 56 was the maximum after leaving the briefing screen with a maximum of ~85 in the debriefing. Performance in cockpit was 45-55 fps which looks understandable for your setup. Since I have no personal experience with AMD Crossfire I will leave a judgement to other people but I would suppose in medium term you would be happier with a strong single GPU than with two low-level GPU's (Simply my personal opinion!)

Have you tried LCtrl+LAlt+Pause?

Because a simulation of a specific plane variant doesn't implement features that are not there in RL. :music_whistling: Similar to those demands for Bison upgrades for the 21bis only because todays variants use it.

Maybe you even tried it but have you ever tried shutting down CCC before the start of DCS? Did some magic for me during the old days...