BravoYankee4

This I assume....

Or try HawgTouch / Ikarus :thumbup:

Well, having a PSU rated with higher capacity than needed is not a problem. What exactly is getting hot? Can you elaborate and provide some pics/details?

Is it possible to export the rear view mirror? I have a spare small 9" monitor that would be prefect for that...

He didn't say anything about 2016 ;)

I was just about to request this as well, so I was very happy to find this :)

Yes, they are nice. What you actually do is building a low resolution RGB display Slightly off topic, but here are two examples of what can be accomplished with just an arduino and a few addressable LED's: [ame] [/ame] [ame] [/ame] P.S Sorry for the music and noise in the second video, but it was used at a school disco for 7-10 year old kids :smilewink: By the way, it doesn't have to be RGB. If you use the WS2811 controller you can have three singe color led (of whatever color) connected. WS2812 is as LED with the WS2811 built in.

It wasn't supposed to be rude or anything like that. As always it is never a good idea to be ironic or make jokes on a forum, escpecially if it isn't in your native language. Neither did I notice that your post was edited.

Since you borrowed my screenshot, used in a previous thread asking about exactly this. Couldn't you have bothered to actually read the answers in the thread as well? :music_whistling: http://forums.eagle.ru/showthread.php?t=150196&

You can use addressable LED's like WS2812 - then you only need 1 output pin on the arduino and can have hundreds of LED's.

Finally got it working :) McMicha from the SDA team did a workaround for the Ikarus software and also helped me change the DCS-Bios export. If anyone is interested let me know.

1 : Anapa 2 : Krimsk 3 : Krasnodar 4 : Pashkovskiy 5 : Maykop 6 : Adler 7 : Mineralnye Vody 8 : Nalchik 9 : Mozdok 10 : Beslan 11 : Tbilisi Vaziani 12 : Tbilisi Lochini 13 : Kutaisi 14 : Senaki Kolkhi 15 : Kobuleti 16 : Batumi

So it is a digitial joystick (with 4 switches) then? Makes sense since that would allow a much simpler data transmission protocol.

Just realised that the 1.53 upgrade resetted the init.lua file (since it seems to have been updated). But thanks also to Heinz and Micha who send the files via email. Anyway, here is an example of having extra viewports for the ASP gunsight (bottom left corner) and the radar (bottom right corner). I'm not gonna fly with this setup - it is just a proof of concept. Eventually (when I have a better PC hardware configuration) I will export the radar to the second monitor, so I can have it embedded in the HawgTouch profile with all the other instruments and gauges.

There is a lot of information/data to digest in this thread and a lot of people having good insight in both the airframe and the doctrines sharing that. So we have good possibilities to be prepared for this module when released and enjoying all systems from day one :) After that post with the RWR PDF there are two more about the countermeasure pods (if you haven't seen them yet).

Nice, but what about the second seat for the RIO? :)

The RWR indicators are embedded in the CI (see picture). The functionality is described in one of my previous posts (http://forums.eagle.ru/showpost.php?p=2664381&postcount=1028).

It isn't really fair to compare the Viggen and A-10 doctrines. The first one was built to counterattack a full Soviet invasion. An invasion probably supported by fighters and very capable A-A units. So yes, go in low, hit hard, haul ass and get back home to reload and do it again, at another location from another direction. Flying an A-10 over the desert fighting a low tech army with AK-47's and some manpads is another story. Then you can linger in the area waiting for the next stupid to pop up and meet the 72 virgins as an instant result... :music_whistling:

I flew that sim once (when it still was available for non-members) and it is a great experience. Even though it is based on FSX :music_whistling: There is a great amount of manhours behind that simulator, both software (maps, terrain objects etc.) and all interfaces between the sim and hardware. So I can understand that most members don't want to start all over again. But, having a DCS module of LNS standards in this cockpit would be awesome. But there is also a great value in having all of Sweden available with a high detail in the scenery (as it is now in FSX). So, a though choice for Swesim to handle.

I believe that is a known bug for that particular mission.

HawgTouch can be downloaded here: https://github.com/s-d-a

I have posted this a while ago, but seems to be proper to do it again :) http://www.museeairespace.fr/aller-plus-haut/panoramas-360/360-cabines-de-pilotage/panorama-360-saab-sk-37e-viggen/ Not AJS, but very similar (missing some combat equipment and some things are dummies).

Thanks, wasn't aware of that function. Will it replace deleted files or is it a kind of "factory reset"? Meaning that all edited lua-files will be restored to default?

The good news, I have learned tonight how to export viewports to another monitor. I want the radar to be on my second screen, embedded with all the other gauges (HawgTouch). A bit daunting at first, but going through the "Dummies guide for monitor setup" a few times I finally understood the concept. Also learned that the gun sight could be exported - wich is good if I want to fly in "HUD only view". The down side. It takes a lot of fps exporting the radar to the second screen (actually fourth) since my setup is 1280*1024 * 3 monitors plus one 1920*1080 screen for the gauges. The total resolutionen needed is to much for my setup and the fps goes below 30. So I need to reconsider that... Finally - could someone please help med getting the original data from the following file: Mods/aircraft/MIG-21bis/Cockpit/HUD/Indicator/init.lua Had to many init.lua files open at the same time making changes in the wrong one :poster_oops:

Well, not that complicated. An Arduino MEGA and DCS-BIOS is all you need. Takes 5 minutes to configure :) The Thrustmaser MFD's has 28 switches - and the MEGA board has 54 digital inputs. So either skip some of the (rarely used) buttons, or add an additional board (that can be used for other in-/output in the cockpit.