SuperTonique

Hi xoomigo ! So, I'm back on this topic. Could it be possible for you to explain me how I can add the Phanthom F4 in the files of the old version of DCS-COINS ? In fact I'm steel using the TouchPortal V3.1 because I can modify all my interfaces as I wish. If I use the touchportal V4, I need to make again all my interfaces and it's to heavy. Thank you for what you can do for me and for your answer. Best regards,

Hi pilots ! Just a question to the F4 conceptors : - Could we expect a futur Ground Speed indicator in the pilot cockpit ? Thank's for your answer !

You're right, I hadn't thought that the option had been validated in the last update. Without the option, everything works normally now. Thanks for the help!

Hello guys ! First of all, I'd like to say to the designers of this mod that the Mirage F1 is a very flyable aircraft and it is very plaisant to fly with. But, because there is a "but", I have notice a small bug on the preset channel pannel red and on the U and U-VHF push buttons use. Here is the problem step by step : - The U-VHF push button is selected (green light on), - The green preset channel panel is set on the right channel of the ATC, - The red preset channel panel is preset on any channel except channel 20, - When I press the F1 key (or F3 in compliance with the radio menu presented) to send my radio message, the Red channel number automatically changes to 20 and the Red U push button changes in the ON position with the U-VHF push button passing OFF. - If I try to select again the U-VHF push button on, both buttons (the red U and the green U-VHF) lock in the ON position simultaneously. - Then, with both buttons locked in the ON position(red and green lights ON), it is no longer possible to select one or the other. They are locked ! So I can't say on which radio station I'm transmitting, Red or Green... - If memory serves, only one or the other of the two buttons can be selected. It is not normally possible to have both push buttons in the ON position at the same time. This is the basic principle of selection. Am I the only pilot on DCS to be faced with this problem? if anyone has an idea or even a solution, I'm interested. Thank you and enjoy your flights

GOD is living ! Many thanks !

Understood ! Thank's ! I can't understand the reason why its possible to push it if it would'nt do anything... May be in the future. A mystery... The F4 is a very pleasant airplane to fly. Have nice flights !

Hi ! At the center of the Delivery Mode Knob is a push button libelled "Nuclear Push to Jett". This push button is usable with the mouse on the screen. I'd like to give an assignated key on the keyboard but I can't find this "Nuclear Push To jett" button in the controls list. Is anybody knows how is named this push button ? Thank's for help !

I think you're right. Thank's !

In the real flight manual, we can read that the full flaps Take Off is prohibited. So, how can I take off with the 1/2 flaps position ? The logic given in the Heat Blur manual is not in concordance with this restriction. On ground, with the flaps/slats control in the middle position, the flaps and the slats are fully down and out. No intermediate position is available. Any idea about the problem ?

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 ?