SuperTonique

Thanks a lot for your answer !

Sorry about my non-understanding... but what about "FXO and Metashader floders" ? Where are they positionned ?

I've found a screen setting with the "anti-aliasing" option that gives a more or less correct result. I'll try to push the settings a bit further. What I can't understand is why, before a DCS upgrade, all the settings are fine and then, after the upgrade, you have to adjust everything again. If you have any ideas, don't hesitate!

Yes ! I know that and I have yet installed this update... no change !

Hi pilots ! I've noticed that since NVIDIA is coupled with DCS World, all small white information or object on the screen are flickering despite the various screen settings. Have you the same problem ? it's very unpleasant...

Good news ! So, I think that the Touch-Portal V4 will be required to install the next version of DCS_COINS ?

I remember ! So, here is the result. I have run DCS and I've choosen the SA342 mod. And after that, I've proceed with the cmd lines following. To give you all information, When I select an other mod, Touch-Portal works properly. I see that on one of lines, the aircraft is named "SA" then "SA34"... Thank you for your analyse. Microsoft Windows [version 10.0.19045.4046] (c) Microsoft Corporation. Tous droits réservés. C:\Users\Admin>cd \Users\Admin\AppData\Roaming\TouchPortal\plugins\Munt.G_DCS-COINS C:\Users\Admin\AppData\Roaming\TouchPortal\plugins\Munt.G_DCS-COINS>dcs-coins -v DCS-COINS Version 3 (2210.07): Verbose mode enabled. 2024-04-03T19:42:04.101Z [INFO] dcs-bios-api: parsed aircraft JSON - A-4E-C 2024-04-03T19:42:04.107Z [INFO] dcs-bios-api: parsed aircraft JSON - AV8BNA 2024-04-03T19:42:04.108Z [INFO] dcs-bios-api: parsed aircraft JSON - CommonData 2024-04-03T19:42:04.108Z [INFO] dcs-bios-api: parsed aircraft JSON - MetadataEnd 2024-04-03T19:42:04.109Z [INFO] dcs-bios-api: parsed aircraft JSON - MetadataStart 2024-04-03T19:42:04.115Z [INFO] dcs-bios-api: parsed aircraft JSON - Mi-8MT 2024-04-03T19:42:04.121Z [INFO] dcs-bios-api: parsed aircraft JSON - MirageF1 2024-04-03T19:42:04.125Z [INFO] dcs-bios-api: parsed aircraft JSON - SA342 2024-04-03T19:42:04.131Z [INFO] dcs-bios-api: parsed aircraft JSON - VNAO_T-45 2024-04-03T19:42:04.141Z [INFO] dcs-bios-api: UDP client listening on 0.0.0.0:5010 2024-04-03T19:42:04.143Z : Munt.G_DCS-COINS :INFO: Connected to TouchPortal 2024-04-03T19:42:04.145Z : Munt.G_DCS-COINS :DEBUG: Info Message received 2024-04-03T19:42:04.157Z : Munt.G_DCS-COINS :DEBUG: ShortID Connector Notification received Aircraft: []: Unavailable in installed DCS-COINS module list! Aircraft: []: Unavailable in installed DCS-COINS module list! Aircraft: []: Unavailable in installed DCS-COINS module list! Aircraft: []: Unavailable in installed DCS-COINS module list! Aircraft: [SA]: Unavailable in installed DCS-COINS module list! Aircraft: [SA34]: Unavailable in installed DCS-COINS module list! Aircraft: [SA342L]: Unavailable in installed DCS-COINS module list! Aircraft: [SA342L]: Unavailable in installed DCS-COINS module list! Aircraft: [SA342L]: Unavailable in installed DCS-COINS module list! Aircraft: [SA342L]: Unavailable in installed DCS-COINS module list! Aircraft: [SA342L]: Unavailable in installed DCS-COINS module list! Aircraft: [SA342L]: Unavailable in installed DCS-COINS module list!

I thank you so much for your answer. I'm sorry, but I don't understand "Please post the output of "dcs-coins -v" when you have the SA342 up and running". Where can I pickup the output of "dcs-coins -v" ? And What about ? Be kind to explain me...

Hello everyone! I'm a Touch Portal user. I'm trying to make an interface with the new Gazelle SA342 (DCS V 2.8) that the latest version of DCS gave us just before the last version of DCS 2.9. Unfortunately, the actual Gazelle's DCS-COINS module doesn't seem to work. Is there any change on the last version of the Gazelle that could change something in the DCS-BIOS and the DCS-COINS funtionnallity ? Is anyone that had the problem and is there a solution, or do we have to wait for the more advanced developers to create a DCS-COINS module compatible with this new SA342 version? Thanks for your answers and happy flying!

I've installed the latest version of DCS (2.9). Since this installation, the quality of the radar screen on the A4E-C (V 2.2) has deteriorated. The echoes presented are no longer fine but are symbolised by coarse green dots whose brightness cannot even be adjusted. Am I the only one with this problem? Today, the Radar is unusable...

So ! We are waiting ! We know that the job will be done ! Thank's for work.

Thanks for your answer. Could you tell us the solution to use or do we have to wait for the next Mirage F1 version ?

Hello guys ! Since the 2.9 DCS new version, the modifications on the "limits_6DOF" line in the "Mods/aircraft/MirageF1/ViewCmn.lua" file doesn't work any more. So, now, I'm not able to capture parts of cockpit to create specific interfaces to use with "Touch Portal". It still works with the AV8BNA and with the A4E-C... Is there any other solution to modify the limits of camera view on the Mirage F1 ? Is it a bug ? Or a volunteer modification ?

I have the same problem with the Mirage F1. Since the 2.9 DCS new version, the modifications on the "limits_6DOF" line in the "Mods/aircraft/MirageF1/ViewCmn.lua" file doesn't work any more. So, now, I'm not able to capture parts of cockpit to create specific interfaces to use with "Touch Portal". It still works with the AV8BNA and with the A4E-C... Is there any other solution to modify the limits of camera view ?

Bonjour à tous ! Je découvre le module du Mirage F1. Très belle réalisation. En qualité d'ancien navigant pendant 38 ans, j'ai toujours eu l'occasion de voler sur des avions qui m'indiquaient la consommation instantannée des moteurs. Or, sur le Mirage F1, il semble que la consommation instantannée soit un secret bien gardé ! Pas d'indicateur qui permette d'anticiper la consommation. On vole jusqu'à ce que le moteur s'arrête ? On a juste ce que l'on a consommé. Mais ça, je dirais qu'on s'en moque parce que ce carburant consommé ne nous sert plus à grand chose ! Je préfèrerais savoir ce que je suis en train de consommer à l'instant T. Plus sérieusement, y-a-t-il parmi nous tous un ou plusieurs anciens pilotes de Mirage F1 qui pourraient nous expliquer comment ils opéraient pour gérer et prévoir la consommation de carburant, tant à la préparation du vol qu'en vol ? Merci à tous ceux qui pourront éclairer ma lanterne. J'avoue être très gêné de voler sans vraiment savoir ce que je consomme et ce que je dois prévoir pour les minutes qui suivent. Bons vols !