Gryzor

I´m on Windows 10, no luck with this... any help please? with previous NVIDIA drivers I could change it by HDMI cable change trick, but now it seems not possible. Thanks.

All of us have 30% degradation in performance problems. Look BEARTRAP F-15 campaign, it is completely unplayable, stuttering every 3 seconds it is there. Reported many times.

I think that now we cannout use the trick of changing HDMI cables, due more recently updated NVIDIA drivers... any help please?

Meanwhile ED do not solve bugs like model vibility, A-10TGP IR, AI, and performance impact in FPS... which it is worse in each update, i will not buy anymore. That´s over. (F-18 included). Like I said, some modules in alpha state would not last forever in time (2 years for merge nevada....come on...and meanwhile, devoloping full WW2 product leaving other things unfinissed), If I buy early Access products thats do not means I have to wait many years to have a full product I paid with my money. Solving bugs must be a obligation to customers who support and pays money, not a priority.

No performance gains for me in 1.5.7 update 1

Updated It. It is not solved for me, in fact it seems is the same situation in comparison with 1.5.7 previous version. If not worse, let me say for example F-15 FC3 Bear Trap Campaign it is unplayable now (stuttering goes every 3 seconds from 70 fps to 25 fps or worse), if we compare to 1.5.6 situation where performance as smooth as silk with almost no sutter.

Finishing a product that has been paid (in my case, I spent about 500€ also, between aircrafts, terrains, etc), even a early access product, MUST be an obligation to customers, not a priority, including alpha or early Access that cannot last forever (mos of them, nearly to 2 years now)

Yes please give us that option, flight in Spitfire VR is not good with ASW

Im not referring to this texture error in my first post.

I noticed with 1.5.7 beta than cockpit reflections looks really weird, practically on all planes. It´s like some graphics properties were copied from 2.1.1. versión (maybe prb texture attributes?), Before, only plane affected in 1.5.6 was su-27, specially reflections on some dials or hud (in some circunstances, cockpit was opaque), In addittion to this, VR performance is not so good if we compare with 1.5.6, Please ED, in the next 1.5.7 public version, return cockpits reflection to previos state

Llevo con sims desde 1988, empecé con spectrum 48K, gunship y F-15 strike Eagle (I). En PC, con 8086 4.77 GHz 640Kb y FALCON AT (en gráficos CGA de 4 colores...), hasta la fecha... y ni un solo SIM que fuese a unos FPS decentes con equipos "normales" para la epoca, buff... en todas ellas. Recuerdo un sim "EF2000", avanzadísimo para su tiempo y si conseguias 20fps eras un privilegiado. Luego salió en GLIDE 3DFX y aun así, cuando se juntaba AAA con varios cazas el stuttering era horrible... Todos igual. FSX, FS98, FS2000, F-14 Fleet Defender... Falcon 4.0 ... F117 Nighthawk, F-15 strike Eagle II, todos ellos... hasta que no pasaban 3-4 años, no los podías mover decentemente, y con maquinones nunca conseguias casos de fluidez estable al 100%. En casos como Falcon 4.0, hasta 10 años incluso sin conseguir que la campaña no diese "tirones" en ciertas ocasiones. También ocurre que la propia complejidad de este tipo de software, unido a las reducidas plantilla de desarrolladores que cuentan con pocos recursos para optimizar el rendimiento y motor gráfico (si comparamos con juegos triple X con presupuestos de 100M$), es otro factor que no juego mucho a nuestro favor. A día de hoy, en mi opinión, y si comparamos con el histórico, creo que conseguimos mover este tipo de software con cierta fluidez (comparativamente hablando), hace 20 años soñábamos con sims con tasas de 30 FPS y ahora este rendimiento es inaceptable... ¡¡¡ es lo que tiene este mundillo !!!, también, evidentemente, somos mas exigentes por regla general. Salu2

Pues en mi caso, 7700K a 5 GHz con ram 32GB DDR4 3200 MHz, SSD 2TB 850 EVO y 1080TI a 2000Mhz Core, me va de lujo, en modo RV con oculus rift algún que otro tiron en normandia. En modo NO-VR, me va como la seda, ni un solo stutter 60 fps estables. Todo el mundo sabemos lo exigentes que son los sims, desde hace décadas siempre ha ocurrido lo mismo. Moraleja: quien algo quiere, algo le cuesta.

In addition, in2.1, I noticed that the mon do not generate lighting, opposite with 2.0 and 1.5 versions. Full mon nights seems very strange now, also the mon does not generates any reflect in wáter.

Thanks

Primero ten en cuenta que ya se te avisa por lo que pagas, que es un producto Alpha, como dicen los americanos "up to you". Y te agradecería también evitar similitudes del tipo "ludópata" o "yonky" a la personas que tenemos un hobby y/o afición, cada uno se gasta el dinero como le da la gana, y no tiene nada que ver con otros temas que son muy serios.

Also, the excesive brightness in VR makes nearly imposible to read HUD or even collimated sights from WWII planes. In addition, I had many CTD when exit from a mission to briefing in VR mode, that CTD do no happens in monitor 2D view. Please dev, fix asap VR performance in 2.1 (maybe a hot fix??), I know this is a alpha however we spends a lot of weeks waiting normandy or other improvements, personally I spend a lot of money, even two years ago when nevada was launched I remember it did not have so many bugs. Thanks KR

Long loadings and 1-2 secons freeze when pannings or loading other map zones. Not this freezes on 1.5.5!

I have in 1.5.5 and 2.04 the same error (D3DKMTCloseAdapter), specially when finish a mission with plane crashing into the ground. Tried everything, repairing, DDU, no-mods, no overclocking... In 1.5.4 and 2.03 did not have this CTD. Logs.zip

I have in 1.5.5 and 2.04 the same error (D3DKMTCloseAdapter), specially when finish a mission with plane crashing into the ground. Tried everything, repairing, DDU, no overclocking... In 1.5.4 and 2.03 do not have this CTD. Attached logs DCS-20161216-222334.zip

I´ve perfect celaned system from startup but I have same problems after 1 or 2 two missions.

I found a solution, simply delete TAB key from UI menu and quit. Next time you open DCS World TAB key will work, only you have to do is remap chat function to another key. Regards

I have that lag in menu, sometimes clicking a button lasts 15 secons or more. No bitdefender installed or others 3rd applications It is specially critic after a mission witw several units, believe this problem it is not from my side My config: clean W7, 32GB Ram, SSD (Samsung 2TB), 4960x clocked to 4.5 GHz (hyperthreading disabled) and TITAN X Attach DX_DIAG DxDiag.txt

I noticed than, in night, that flares and other lights dynamic sources (gear lights) do not work in 1.5.4; looks like some the same bug of previous versions (I believe 1.5.1...), hope tan in release versión this will be fixed.

It is related to artillery fire, stuttering every 2 seconds when sevaral groups are active

Me too it happens in missions which lasts 20-30 minutes, after quit sometimes hangs (infinite loading screens), other times takes 1-2 minutes to get main menu. Memory leak?