DTC for DCS - new version 7.2.0 - Apache added

[WHOGX5]

2 hours ago, Vigo68 said:

where is source? p.luis on github has RC13 and exe is RC12. thx

 

RC13 is the latest version, I think they just forgot to update the version number in the UI. I'd refrain from using RC13 though, VirusTotal lit up like a Christmas tree last time I ran RC13 through it. I still use RC12.

[Biwi]

Hi there, first thank you so much for creating this amazing tool ! 

As I was creating commcards for each map we use, I wanted to create RADIO presets for each commcard, and I stumbled upon an issue with VHF FM band frequencies :

If you want to enter say 35.45 (our A-10 squadron tactical freq), you type 035.45 in the DTC software and then you upload it to the jet it works fine, BUT if you save the preset to a JSON and open this file, it has turned into  354.50

Could you please fix this ?

 

Tahnks again,

 

Best

 

Edited December 19, 2022 by Biwi

[FireNLD]

9 minutes ago, Biwi said:

Hi there, first thank you so much for creating this amazing tool ! 

As I was creating commcards for each map we use, I wanted to create RADIO presets for each commcard, and I stumbled upon an issue with VHF FM band frequencies :

If you want to enter say 35.45 (our A-10 squadron tactical freq), you type 035.45 in the DTC software and then you upload it to the jet it works fine, BUT if you save the preset to a JSON and open this file, it has turned into  354.50

Could you please fix this ?

 

Tahnks again,

 

Best

 

 

Makes sense, The radio bands of the viper dont cover 35Mhz. They are as following:
COMM 1 ARC164: 255-399.975MHZ
COMM 2 ARC222: 108-151.975MHZ 

Edited December 19, 2022 by FireNLD

[WHOGX5]

9 hours ago, FireNLD said:

Makes sense, The radio bands of the viper dont cover 35Mhz. They are as following:
COMM 1 ARC164: 255-399.975MHZ
COMM 2 ARC222: 108-151.975MHZ 

 

This is incorrect. The AN/ARC-222 can also tune FM bands from 30-87.95 MHz.

[FireNLD]

4 hours ago, WHOGX5 said:

This is incorrect. The AN/ARC-222 can also tune FM bands from 30-87.95 MHz.

Why haven't i got it to work. Interesting. 

[Biwi]

No the AN-ARC-222 works in the FM range : FM: 30-87.95 MHz; AM: 108-155.975 MHz (108 - 115.975 MHz RO) and it perfectly works within DCS world, you probably are setting something incorreclty. In the ME, set a vehicle on the same coalition and give him the order to send a message on an FM freq (don't forget to select FM in the appropriate field) tick "loop" and add your .ogg file, then put your helmet on and tune to its frequency and you'll hear it. 

Edited December 21, 2022 by Biwi

[FireNLD]

Yeah probably fumbled something. Works fine. 

[solidusfox]

Have this issue and I have tried previous fixes such as opening the ports, turning firewall off, deleted DTC including every script for it and starting fresh any help would be much appreciated

null

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:43001
   at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
   at DTC.Models.F16Upload.Load()
   at DTC.UI.Aircrafts.F16.UploadToJetPage.btnUpload_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4515.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
DTC
    Assembly Version: 3.2.0.0
    Win32 Version: 3.2.0.0
    CodeBase: file:///C:/Users/Solidusfox/Desktop/DTC/DTC.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4550.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4536.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4395.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4341.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4161.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4161.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
Newtonsoft.Json
    Assembly Version: 13.0.0.0
    Win32 Version: 13.0.1.25517
    CodeBase: file:///C:/Users/Solidusfox/Desktop/DTC/Newtonsoft.Json.DLL
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4590.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4161.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Runtime.Serialization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4536.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4584.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

nullnull

[Raviar]

On 12/29/2022 at 8:14 PM, solidusfox said:

Have this issue and I have tried previous fixes such as opening the ports, turning firewall off, deleted DTC including every script for it and starting fresh any help would be much appreciated

null

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:43001
   at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
   at DTC.Models.F16Upload.Load()
   at DTC.UI.Aircrafts.F16.UploadToJetPage.btnUpload_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4515.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
DTC
    Assembly Version: 3.2.0.0
    Win32 Version: 3.2.0.0
    CodeBase: file:///C:/Users/Solidusfox/Desktop/DTC/DTC.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4550.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4536.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4395.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4341.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4161.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4161.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
Newtonsoft.Json
    Assembly Version: 13.0.0.0
    Win32 Version: 13.0.1.25517
    CodeBase: file:///C:/Users/Solidusfox/Desktop/DTC/Newtonsoft.Json.DLL
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4590.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4161.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Runtime.Serialization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4536.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4584.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

nullnull

i faced to same issue, didnt have any issue with it until the last windows update i guess 
@SFJackBauer any chance for new version?
 

Edited January 3, 2023 by Raviar

[Elephant42]

This is an example of that very rare commodity - an open source project that builds cleanly OOTB.  Many thanks for sharing and kudos on the design.

 

[RogueSqdn]

I don't suppose we could get the next version dumping the skeuomorphism, could we?

That and the always on top being active as it's launched kinda bugs me.  Does it bother anyone else?

 

Functionally, since it can't be changed in cockpit, I don't suppose there's a way to change program 6 (the slap switch) in the Hornet, is there?  Otherwise, I think I'll have to stick to lua edits for my CMDS programming.

[Raviar]

I tried to change the port to 43002 in the script and "dtc-settings.json" but got the same error, disabling the FW or adding the port and application in the FW rules didnt help, I checked with netstat and the port consumed by DCS itself.

Here is the dcs.log on default port

2023-01-04 11:46:30.596 INFO    WWT (Main): Export start!
2023-01-04 11:46:30.596 INFO    DCS-DTC (Main): Opened connection
2023-01-04 11:46:30.596 INFO    WWT (Main): Export start!
2023-01-04 11:46:30.596 ERROR   DCS-DTC (Main): Error opening tcp socket - address already in use

nullhere is the application exception and stack trace:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:43001
   at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
   at DTC.Models.F16Upload.Load()
   at DTC.UI.Aircrafts.F16.UploadToJetPage.btnUpload_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4515.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
DTC
    Assembly Version: 3.2.0.0
    Win32 Version: 3.2.0.0
    CodeBase: file:///C:/DCS-DTC-3.2.0/DTC.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4550.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4536.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4590.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Newtonsoft.Json
    Assembly Version: 13.0.0.0
    Win32 Version: 13.0.1.25517
    CodeBase: file:///C:/DCS-DTC-3.2.0/Newtonsoft.Json.DLL
----------------------------------------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Runtime.Serialization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4536.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4584.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

[malarcky]

I am getting this trojan notification when trying to download the RC13 from p-louis fork

Anyone can confirm it is safe?

Edited January 6, 2023 by malarcky

[WHOGX5]

18 hours ago, malarcky said:

I am getting this trojan notification when trying to download the RC13 from p-louis fork

Anyone can confirm it is safe?

 

DON'T USE RC13! Use RC12 instead. A lot of sketchy stuff was added in the RC13 patch which will compromise your PC.

[malarcky]

On 1/7/2023 at 3:40 AM, WHOGX5 said:

DON'T USE RC13! Use RC12 instead. A lot of sketchy stuff was added in the RC13 patch which will compromise your PC.

Damn, already opened, I hope its nothing bad

[RogueSqdn]

It's nothing, false positive

[WHOGX5]

On 1/8/2023 at 2:33 PM, RogueSqdn said:

It's nothing, false positive

Quote from a member in my community who's infinitely more knowledgeable than me when it comes to IT stuff:

"It connects to HTTPS servers on the internet which are part of a CDN, it seems to include packed / crypted data and it creates guard pages..."

I trust his judgement and I'd rather be safe than sorry. He's checked previous releases of DCS DTC as well since they all give off anti-virus warnings, but RC13 was the first patch that he told us, in no uncertain terms, not to download.

[Raviar]

23 minutes ago, WHOGX5 said:

Quote from a member in my community who's infinitely more knowledgeable than me when it comes to IT stuff:

"It connects to HTTPS servers on the internet which are part of a CDN, it seems to include packed / crypted data and it creates guard pages..."

I trust his judgement and I'd rather be safe than sorry. He's checked previous releases of DCS DTC as well since they all give off anti-virus warnings, but RC13 was the first patch that he told us, in no uncertain terms, not to download.

I went through the all code diff, line by line between two branches. I didnt find anything and I dont think there is anything even close to the claim! can you please ask your community member to let us know which line of the code would/may do that?

its only added Hornet, Apache .. support with some other changes
The only communication is on localhost via 127.0.0.1 

These guys spent hours in coding and testing for FREE, please dont under question their valuable efforts with such claims without proof! even if you give us pcap or any network pack sniff i would go through it! 

Edited January 12, 2023 by Raviar

[Habu_69]

My search results were fruitless, so I will ask here for a detailed explanation of how to enter JDAM/JSOW pre-planned target coordinates in the Hornet. Official guide is a little sketchy.

[XCNuse]

Up/Downgraded to RC12 and now a handful of my group is now using this mod on the Hornet and Viper.

 

I wish I knew or something was stated that you had to have the HSI open on the right DDI for it to work..... it seems illogical to me that would even be necessary in the first place.

But, for anyone struggling to get this thing to work, make sure the HSI is open on the right DDI (weird I know, I've never had it open there on the ground personally). And then  it started to work just fine.

 

Wondering if this project though is dead and should just shift everyone over to "The Way" until ED can come up with a solution.

[jstnj]

I need this for the A-10C

 

Thanks for the contribution regardles  

[lethal205]

19 hours ago, XCNuse said:

Up/Downgraded to RC12 and now a handful of my group is now using this mod on the Hornet and Viper.

 

I wish I knew or something was stated that you had to have the HSI open on the right DDI for it to work..... it seems illogical to me that would even be necessary in the first place.

But, for anyone struggling to get this thing to work, make sure the HSI is open on the right DDI (weird I know, I've never had it open there on the ground personally). And then  it started to work just fine.

 

Wondering if this project though is dead and should just shift everyone over to "The Way" until ED can come up with a solution.

This app has way more functionality than TheWay, especially for the Viper. Not to detract from TheWay at all because it's a fantastic app as well, but you can't edit counter measures, radios, joker/bingo, laser codes, etc. with it.

 

That said, the OP doesn't appear to have worked on this in quite a while, so I wouldn't keep your hopes up for future updates.

Edited April 23, 2023 by lethal205

[Chain_1]

On 4/23/2023 at 9:48 AM, lethal205 said:

...so I wouldn't keep your hopes up for future updates.

 

Especially considering that ED is actually working on the DTC, according to the roadmap.

[ST0RM]

Getting an error when using the DTC program, ever since MT was implemented. Could be Windows related, but figured posting up my error log could help.
 

DTC_Error.docx

[SFJackBauer]

Sup everyone.

Sorry for the blackout. Things in life happened and I ended up taking a break from DCS for a while. The break then got longer, then longer, and then longer until now. I did not had headspace to think about this, but I should have at least left some message here.

In any case, this is done in a completely voluntary basis. I added p-louis way back as a contributor to the repository since he volunteered to implement the Hornet and the Apache, and I can see he has done a lot in that regard. I will try to dedicate time to support what has been done and improve in any way that could be done, but the primary module I fly is the F-16 so that is where I spent more time developing.

Now I want to address some topics:

- Error about TCP connection on port 43001

The DTC software works this way: It has a bidirectional connection to DCS, to send and to receive data. To receive data, the DCS lua script opens a UDP port 43000, which the DTC software reads. This port is only read when doing waypoint capture from DCS. On the other hand, to send data, the DCS lua script opens a TCP port 43001, and the DTC software tries to connect to this port when doing the upload to jet. If the DCS lua script does not create the port, the DTC software will error when trying connect to it.

Therefore the most common reason for this error is just an improper installation of the LUA script in the Saved Games folder. If you follow the install instructions it should work. This is the same way other mods that needs to read/send data to DCS work.

- Virus warnings

Virus detection is a complex subject and the antivirus tools uses a series of heuristics to flag an executable as malicious. For example, the fact it needs to connect to the lua script may be a factor to flag it. Also there is no installer and Windows tends to flag executables downloaded from the internet as suspicious. Its a fact people use liberally other mods (from DCS and other games) without checking its source code and the reason they do not get flagged is just because an installer is used... and thats fine because security is also a function of the perceived trust and the empirical evidence of the software actually doing something weird. To be honest, the safest way if you are paranoid is to never download any executable from the internet at all, but who lives like that? In any case the DTC code is open and anyone can always inspect it and/or compile on your own machine if you are willing to go to that length. Or... not use it at all.

With that said, I will investigate adding an installer if this just means making it less bothersome for people who actually wants to use it. I've inspected the latest version of the code and there is nothing implemented beyond the purpose of the software.

- Discord

I am considering opening a Discord server dedicated to this mod, so people can discuss it, suggest features and support each other. Is it something worthwhile? I would like feedback on this.

 

Cheers.