Trubshaw

Can anyone throw some light on what is going on here please. Had this app for quite some time working perfectly on two tablets. About 6 months ago it stopped displaying info from the game. eg: F16 DED data F18 UFC numbers. The external tablets communicate to DCS and have an effect in game. BUT DCS does not communicate with the tablets. Pitor has had a look at this for me with no success he is a great developer and very approachable. Any ideas what has gone wrong or what I should check? Thanks Anybody else has this issue?

Do you have to have DCS Bios running for this to work?

I had a problem once where the LEDs in the bit that sits on your monitor burnt out...had to buy a complete new one. Natural Point were not interested in just selling me that part.

I also have 3 monitors and use NVidia surround to merge them into one screen. Is that what you use? It may be an aspect ratio issue, as I have not noticed this effect. Next time I boot it up I will look at what my aspect ratio is.

...and to be fair not mentioned in the patch notes..... ..but have you seen anything? Mr. Big. "Biggs"?

Has any pilot noticed any additions? The patch notes did not include anything about the map. If this is so then I am disappointed that a whole month goes by and an early access map does not seem to have progressed.

Really struggling to get this to work on my PC. Watched the videos a few time reduced my Export.lua to only the code for this plug in with no joy. DCS Comms won't connect Please tell me; Do I need to put the IP of my PC in somewhere? Do I need to open ports in my router? Or any suggestions as to what I am doing wrong..thanks in advance.

These are study simulations. So can I suggest you look at Chuck's Guide for the Av8b and the manual for the aircraft.

This is quite a problem. When you have multiple modules and been flying for many years you invest hours and hours on your key bindings. Any significant hardware change or full re install of windows assigns different id numbers to each usb plug in. I am holding off a re-install of Windows 10 because of this issue. It would be interested to know if there is any easy solution to it. As I see it Oiten is right. But for me to do this, I have rudders, two leo bodnar boards, 2 Cougar MFDs, throttle and joystick. 7 unique USB number to copy down before I reinstall and then on the re build edit the USB ID numbers. Anybody know a better way?

I take my hat off to AvioDev for their continued development of this module. Thanks guys happy coding.

Sorry guys I am with Chuck here. What exactly do you do to make 1 monitor option work? For the record I have 3 27 inch monitors and use Nvidia surround to make them 5760*1080. If there is a better way then please could you spell it out. Thanks

Agreed, fair point well made sir.

Cheers Hunter and thanks for sharing

Thanks for setting up this thread and thanks for the fix and yes it works on my 3 screen set up in 2.5.6. When I say it works I means the TEST lua file in this thread https://forums.eagle.ru/showthread.php?t=143536&page=2 by PIEDROIT. Any more tips for us 3 screen users?

Brilliant development guys...well done!

I use a keyboard under desk sliding shelf for my keyboard.

Was that the series where if you went to pre contact for air to air refueling it said "ALL MAJOR CREDIT CARDS ACCEPTED?" I remember the whole range of flight sims from those days..

Really good to see this update. I have just had a quick fly around and the improvements are obvious. Thanks to the coders.

From this side of the pond guys I wish you well. I have met some good friends through the DCS squadron system. Blue skies.....

You would be welcome, Tricky11, we are a pretty relaxed bunch.

Hey Tyger I am also from Nottingham and so is another member of our squad.

It is that time of year again. The time where the noises and smells coming from swamp central attracts Shrek Squadron members to Ogre’s BBQ. TinTin arrived earlier in the week from The Netherlands and set up camp in the loft. By Friday Woody, Wardie and my good self had gathered for a pre BBQ drink and we encouraged Newy to join us for a Friday night in town. Saturday started with breakfast in Sainsbury’s and by the time Ogre started cooking we were joined by EJay, Draco with significant other, Mr & Mrs Nebs, Balrog, Mr & Mrs Catz and Fretless. Syme made an appearance from Scotland via the speaker in my phone to tell Wardie to go forth and multiply. (rather harsh I thought) BeeKay absent yet again! As you can imagine Mrs Ogre and the green man himself laid on an excellent spread and super hospitality. Drinking and laughing went on well in to the night but I cannot help but think that we have become a little more sedate in our old age. (at least less raucous) Special mention to Woody for making it to his first Shrek gathering and Catz for getting the right date this year. This year marked our 8th annual gathering and I for one look forward to next year. Come and fly with us! SHREK Squadron is an English speaking UK based squadron formed in1998. Flying together for mutual support and training. Our Squadron fly and operate most DCS modules, a select few fly several nights each week and an official gathering of members is every Tuesday night. More details from WEBPAGE http://www.shreksquadron.org/ TEAMSPEAK IP Shreksquadronts.org:9990 Cheers TrubshawRN

Hi Rick50, I have a Saitek throttle set up. You need to understand that there are two versions of the throttle quadrant. The one you get with the yoke has a round connecter that plugs into the yoke directly. I think that if you buy this one you will have to hack into the wires to fit a usb type plug but I am not sure. The second throttle quadrant is a separate buy it is meant be added alongside the yoke throttle to be used for two engine air craft. This second type has a usb connector and can be used completely separate in DCS. Does that make sense? You need to check exactly what you are buying.

We have all been there =Decoy= hope you get some spare time soon.

Hey Heatblur, tremendous to see you included Funkyfrankies and the rest of the communities ideas on key bindings for the Viggen. Thanks to all involved in the reporting and coding.