mikko.1842

Nvidia making things easier for 4000 series customers. Low performance uplift, easy 5000 skip.

I will answer in French, as it seems to be your native language, and it will make things easier. Ta capture d'écran montre une texture générique "missing texture" sur le nez, la verrière, et l'épine dorsale, du Mirage 2000D. Cela signifie que DCS n'arrive pas à trouver la texture de ces structures, pour différentes raisons possibles : - le fichier de texture en .dds est absent, endommagé - le fichier de ta livrée en .lua (celui qui gère l'application des textures) est mal écrit ou endommagé Solutions possibles : - essayer d'autres livrées : si certaines livrées n'ont pas ce problème de texture, c'est que ta livrée est défectueuse - dans ce cas, vérifier que la structure de ton dossier de livrée respecte l'architecture / l'arborescence de DCS - vérifier que ton dossier concernant la livrée contient bien tous les fichiers de texture .dds (retélécharger la livrée si nécessaire, afin d'être sûr de l'intégrité du dossier) - vérifier que le dossier .lua de la livrée appelle correctement les fichiers en .dds (sans faute de syntaxe) - réécrire le dossier .lua si tu repères des erreurs d'appel - si tu es totalement nouveau et que tu ne maîtrises pas les .lua et les .dds, je te conseille de contacter l'auteur de la livrée, afin qu'il corrige lui-même - tu peux aussi demander de l'aide sur des discords francophones, comme celui de la Split-Air par exemple

How is your question related to CJS Super Hornet ??? Anyway, your screenshot is compatible with an lua problem : your DCS is not able to find some files for some textures, so you have the generic missing texture squares. Some hints : - check whether you are missing some texture files ; if nothing is missing, you can read the lua file and try to rewrite it - try other liveries - Split-Air RAF / M2000D mod is based on Razbam M-2000C module... the conflict between Razbam and ED induced some "problems", which will most likely never get fixed

I have zero interest in the F-35A module, BUT, we all know it will sell very well. If it sells well, it will make more money for ED... money they could use to improve some unfinished work and/or introduce more redfor aircrafts. So yes, I think ED, as a company which needs to make money, chose the right direction.

It seems that Virpil encountered some quality assurance problems, hence their delaying for the first batches of new series. Better delayed and fixed, than on time and flawed, I guess... Gotta aim for March.

As a French guy, I can only talk about Rafale. Dassault (aka Rafale's manufacturer) have a very strong policy about their intellectual property. They are very touchy about it, to the point that they will take down any mod that uses the actual name of their aircraft. They have a well known history of taking down Rafale mods in Microsoft Flight Simulator. Same reason why Razbam used "M-2000C" and not "Mirage 2000C" for their DCS module. The other problem would be the required military confidentiality level for lots of Rafale's systems. To sum it up, if you don't pay some humongous amount of money to Dassault, you have zero chance to release a full fidelity module, and it would be a Rafale F1 / block 1 standard at best (pretty close to an airframe without systems).

There are evidences that the diagram is outdated/need correction. Pending modifications.

@Recluse Glad you appreciated it. Thank you for your feedback !

It really depends on your physical settings on your CM3. I can show my settings, but if your detent-plates are placed slightly different from mine, it will be useless to try and copy it. It depends on the planes too. Tell me what plane you are using, and I can try to screenshot my settings.

Thank you for your awesome work and your dedication.

I heard so many sad stories about Winwing's customer service, since their beginnings to nowadays. As good as their product might be, with awesome prices, these stories were a "no go" for me. I don't want to have to fight against a company for my rights. I should not have to, and I don't want to spend my time in endless mails/threatenings/etc... Thank you for sharing your experience, and I wish you the best for the resolution of your problem.

The "AB" value is not implemented yet. It is just a visual "hint" for the future. You still have to make your own user curve and find the threshold for your afterburner to trigger, when the throttle reaches a determined position. With my T50-CM3, I tick Slider-Invert-User Curve, and I input my own values.

This is a well known answer, but then, ED shouldn't call it "Replay". Either they should accept that their "Replay" is a failure, or they should rename it "Debug Video".

The Cyber Taurus is the closest thing to what you are asking for.

Nope, no thrust vectoring animation during replay. It is a known issue.