Arsonist

Well, the time stamp on Pocked Sized post, the time stamp on BillyCrushers edit and the time stamp on your post might give you a hint... :music_whistling:

I also saw similar behaviour for Factorio. Right now you have three different versions for download there, via the "Betas" tab. Also when they released the last major update (0.14) they had basically all minor changes as seperate downloads, which they put out in a short time after the major release and I expect a similar behaviour when they release 0.15 in the upcoming weeks. It was around 10 different beta versions. But on these forums here I've seen it beeing mentioned, that ED have stated they do not release multiple early access versions because it would not be possible with Steam. Maybe it would be a good idea that those people, who claim this to be true, would provide a link to an official ED source with said statement. I assume ED has good reasons for not bringing DCS 2.0.x to Steam but a restriction of the amount of possible early access versions might not be it. On possible restrictions for DLC during early access by Steam: I also don't believe that to be true, given that Studio Wildcard could/can sell Scorched Earth as DLC while Ark is still in early access. Furthermore, I'm not in favor of people trying to advertise the DCS standalone version with "gets updates more frequently" and the like. Those more frequent updates are related to the early access versions for testing, the stable gets the same updates via Steam, just a bit later. However, using an alpha or beta version of a game means that there are bugs to be expected and the developers want feedback on them. It is meant for people who are willingly playing, possibly broken, games to report the issues to the developer to be fixed. It does not help the developer if people play the test versions because of faster updates, without properly reporting issues. A better way could be to point out that the standalone version has more sales, in fact every week. If this is a good strategy, I don't know. I guess it is not, given the threads in this forum of people asking for sales of different modules. But that would be another discussion.

Well, despite the fact that some modules are not available there just yet, using Steam to gift modules to others works like a charm. I gave some modules to my friends without any issue. :thumbup: It might be different on ED's own system, but this I don't know. EDIT: I realised that my reply was not so helpful, so I decided to go into more detail. If you select an item from the Steam store, you can decide if you want to purchase it as a gift for somebody or if you want to keep it for yourself. I you want to keep it then, and only then, it will be bound to your account. If you purchase an item as a gift, you have three different options: sent via email, sent via Steam or keep it in your Steam inventory for later use (meaning 'send the gift later'). You can find more information at the Steam support website. I hope this helps!

Not so much of a question for me. Certainly swedish music! This would fit best, in my opinion! :music_whistling: :D

Dear Leatherneck, your Viggen looks very impressive, totally worth to wait for it! Just one and a half years ago I didn't know anything about the Viggen, but due to the knowledge of the swedish guys in this gigantic Viggen-thread this changed (thank you, guys). Now I just want to fly it...:pilotfly: Thank you very much, for your efforts and all the energy you have put into it! Cheers.

I would like to join, too. I hope that you take greenhorns... :joystick:

Hi Ian, had finally some time to look at my AHCP again. Yes, you are right about the pull-down resistors that I used, based upon tutorials that I've read/watched! :thumbup: Now I changed the setup so that the middle pin is connected to ground and the other two are directly connected to the digital input of the Arduino. Then I changed the part in the Switch.h back to LOW. Everything works fine now. :pilotfly: Thank you very much for your help!

Hello everybody! I'm new to all this home cockpit building and working with electronics, all those switches, wires and the Arduino. I've managed to install DCS-Bios and connect it to DCS (I'm on the 1.5). The master caution example works (after I connected the LED in the correct direction it worked too... :doh:). So, now I'm trying to build a simple AHCP. Unfortunately I'm facing some issues with the three position switches. The IRQ serial script is used as base script, containing the code for the gun/pac switch. For some reason the connect-serial-port.cmd shows only two messages: 0 and 2. Nevertheless, the Voltmeter shows a change in the voltage (1 V or 5 V) at the respective contacts of the switch (1 and 3). I've looked into the switch.h in the library. I suppose there might be an error in the lines 46 and 47. When I changed the values from LOW to HIGH, the connect-serial-port.cmd shows all three messages (0,1,2) for the different conditions of the switch (and it works, as expected, in DCS). Is there an error in the script or did I do something wrong? Cheers. PS: Ian, thank you very much for all your effords to set up such a wonderful tool! :thumbup: