hreich Posted January 21 Posted January 21 For example as A-10 cdu - maybe the screen part won't work but will buttons be available for assignement inside dcs keyoard options...Can somebody test it with DCS? [sIGPIC][/sIGPIC] Pilot from Croatia
speed-of-heat Posted January 21 Posted January 21 If it’s like there others , the buttons and axis are just regular joystick buttons SYSTEM SPECS: Hardware AMD 9800X3D, 64Gb RAM, 4090 FE, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO YOUTUBE CHANNEL: @speed-of-heat
MustangSally Posted January 22 Posted January 22 Of course you can use it as all the buttons can be bound like any other controller. The screen on the other hand won't until support is incorporated by Winwing. Ryzen 9 7950X3D - MSI MAG X670E TomaHawk MB, ASUS ROG Ryujin III 360 AIO 64gig Corsair DDR5@6000, Gigabyte GeForce RTX 4090 AORUS Winwing Super Taurus, Orion2, TO / Combat panels, Collective with Topgun MIP Winwing Skywalker pedals, NLR Boeing Mil Edition Simpit, 55" Samsung Odyssey Ark, Trackir
norman99 Posted January 22 Posted January 22 (edited) Why wouldn't the screen work? My understanding is that it can operate in a 'data injection' mode where the sim sends data to the WinWing software and it populates the displays, (similar to the Hornet UFC & Falcon DED.) But, it also has the ability to operate as an additional monitor, just like the MIP MFDs. In this mode, all you need is to calculate the screen positioning and put the correct data into the .lua file to make it work. Edited January 22 by norman99
hreich Posted January 22 Author Posted January 22 6 hours ago, norman99 said: Why wouldn't the screen work? My understanding is that it can operate in a 'data injection' mode where the sim sends data to the WinWing software and it populates the displays, (similar to the Hornet UFC & Falcon DED.) But, it also has the ability to operate as an additional monitor, just like the MIP MFDs. In this mode, all you need is to calculate the screen positioning and put the correct data into the .lua file to make it work. Yep that's what i would like somebody to try before i click on purchase [sIGPIC][/sIGPIC] Pilot from Croatia
Vakarian Posted January 22 Posted January 22 8 hours ago, norman99 said: But, it also has the ability to operate as an additional monitor, just like the MIP MFDs. How sure are you of this? Nowhere in the published data does it say that.
niru27 Posted January 22 Posted January 22 (edited) 1 hour ago, Vakarian said: Nowhere in the published data does it say that. Data Mode = export script based Streaming Display Mode = ?? If it can work as a monitor, can use it as a A10 CDU. Else someone will have to come up with an export script I'm checking with their support team. Will update with more info Edited January 22 by niru27
Vakarian Posted January 22 Posted January 22 It's the "same" thing. One is where they hook into the simulator and "make" their own data to display, the other is where the data is already build and they "stream" it to the display. No where does it say it's capable of an actual video output, that's completely different thing. The "data" that's made is just a font collection(s) that they then display in the correct position on the display, it's not displaying a video.
MustangSally Posted January 22 Posted January 22 (edited) They stated that A10 screen support will be incorporated by SImappro in the near future Edited January 22 by MustangSally Ryzen 9 7950X3D - MSI MAG X670E TomaHawk MB, ASUS ROG Ryujin III 360 AIO 64gig Corsair DDR5@6000, Gigabyte GeForce RTX 4090 AORUS Winwing Super Taurus, Orion2, TO / Combat panels, Collective with Topgun MIP Winwing Skywalker pedals, NLR Boeing Mil Edition Simpit, 55" Samsung Odyssey Ark, Trackir
MustangSally Posted January 22 Posted January 22 Currently there is no support for DCS in Simappro Ryzen 9 7950X3D - MSI MAG X670E TomaHawk MB, ASUS ROG Ryujin III 360 AIO 64gig Corsair DDR5@6000, Gigabyte GeForce RTX 4090 AORUS Winwing Super Taurus, Orion2, TO / Combat panels, Collective with Topgun MIP Winwing Skywalker pedals, NLR Boeing Mil Edition Simpit, 55" Samsung Odyssey Ark, Trackir
norman99 Posted January 23 Posted January 23 (edited) 10 hours ago, niru27 said: I thought the streaming mode was just an extended display mode, maybe I’m wrong. I know the screen displays the WinWing logo on startup, exactly the same as the MIP MFDs do, so maybe it is technically a monitor display? The real difference I see between the MFDs and these CDUs is the MFDs require 2 cables, one for the buttons and one for the display, whereas these CDUs only use one. This might be one of the limitations that prevent the display operating as an additional monitor? I pre-ordered the 777 CDU, so it’ll be a little while before it arrives, but I’d happy to answer any unanswered questions when I do receive it. Edited January 23 by norman99
niru27 Posted January 23 Posted January 23 10 hours ago, Vakarian said: It's the "same" thing. One is where they hook into the simulator and "make" their own data to display, the other is where the data is already build and they "stream" it to the display. No where does it say it's capable of an actual video output, that's completely different thing. The "data" that's made is just a font collection(s) that they then display in the correct position on the display, it's not displaying a video. 1 hour ago, norman99 said: I thought the streaming mode was just an extended display mode, maybe I’m wrong. I know the screen displays the WinWing logo on startup, exactly the same as the MIP MFDs do, so maybe it is technically a monitor display? Text data is still text data no matter if the aircraft produced it, or SAP calculated it. The data source doesn't change the nature of the transmission. Stream is generally used in the context of videos. In this case it would imply the video of the ingame CDU is streamed to the WW CDU Whatever they meant to say certainly got lost in translation. 1 hour ago, norman99 said: The real difference I see between the MFDs and these CDUs is the MFDs require 2 cables, one for the buttons and one for the display, whereas these CDUs only use one. This might be one of the limitations that prevent the display operating as an additional monitor? If it has an internal USB hub, a single cable will suffice. For DCS, it's probably best to implement the text data interface since video export would trigger IC. Come on ED, please whitelist all the export files!
Recommended Posts