Alex_rcpilot

Yes, guess the sources weren't that reliable eventually. What a pain in the butt restriction. Relay channels: http://www.livestream.com/mickeychen http://www.livestream.com/3GO_Alex http://www.livestream.com/3GO443

Dude, I've just learned there's no such thing as viewer capacity over livestream. We all thought that billeinstein couldn't handle this all for himself. lol

We're also testing several relay livestream links to expand viewer capacity. I will update these links in a couple of hours.

Dear all, China 3GO Cyber Air Force was established on April 26, 2001 by a group of veteran flight simulation enthusiasts. Since then, this organization has thrived over time and grown into one of the most influential cyber air combat communities in China. For the past decade, 3GO has brought the sky closer to an entire generation of Chinese combat aviation enthusiasts. Each year, a growing number of modern air combat fans are attracted to 3GO by its persistent military-grade training standards, well-coordinated team work spirit and supply of highly skilled individuals ready to fight as either friends or foes. As squadrons expand and tactic exchanges diversify, 3GO has also become better known in the international community. In appreciation of those who have supported us all along, we’ve scheduled a massive parade at 13:00 GMT on Satuarday, April 23rd (21:00 local time). 3GO 1st Air Division, 2nd Air Division, 3rd Attack Division, 5th Navy Division, 3GO Air Cavalry Team, the Cube Aerobatic Team and the Black Shark Aerobatic Team have worked together on this parade. A mixed formation of over 40 aircraft from all divisions will perform a low pass over the airstrip, followed by a joint aerobatic display carried out by the Cube and the Black Shark Aerobatic Teams, an attempt probably no other team has ever done before. The parade will be available for live webcast over http://www.livestream.com/billeinstein . Our pilots have gone through days of tireless training in preparation for this event. We are well-tuned and dedicated to present you with an exciting experience. Cheers! China 3GO Cyber Air Force (English mirror: http://bbs.3gofly.com/en)

Yup, same question here. I'm kinda used to having them saved in the installation folder. I clean the album every other month removing some crappy shots so it doesn't fill up my partition, and I don't wanna lose them during system reinstallation. I wonder if there's a way to change this setting back.

Aww....crap, sorry guys. I think I made a mistake, I've actually done it some time ago. The programming I said previously, it's already achieved in Helios thanks to Gadroc's great work. Just add two "interfaces": A-10C as output, and your BU0836 as input. Keep the BU0836 tab active. Go to the output menu and choose A-10C from all those interfaces, unfold "Light System". Find the light you want, say Engine Instrument Panel light. If you wanna control it with your slider 0, then just do some drag n' drop work to bind them together. There might be some minor script adjustment required because you might need to fit the ranges of the two, can't recall exactly, but it's do-able. Look into it and good luck.

You're welcome pitbldr, it helps us all with these discussions.

Oh wow, that's pretty neat work you're doing there. You've got tons more experiences with PC programming than I do. I'm glad that you've got so much up and running, and that it's just a fraction of the big picture. You're right about AVRs and dynamic memory. With all those pointers assigned here and there, it's like building an OS from scratch, at least the memory management part. Good luck with the testing job!:thumbup:

No problem y2kiah. I remember you had a PIC32 board back then. How far did you go with that?

Actually what you were asking is really a good question. It involves what's going on between different modules within a software (DCS) itself, and between different pieces of software. The answer helps everyone get a better understanding of a vast collection of similar software. I'd like to take this chance to learn more from other guys. For the lua part. IMHO, it's like handing a task list to your accountant. It lists all the account numbers and phone numbers needed during work, but this sheet itself isn't money. Then during working hours a phone call arrives that involves one of the accounts on the list, the arranged withdrawals or deposites will be "triggerred" accordingly. The accountant does it all, and you don't need to know which bank she visits to get it done. The task list is like your lua file(s); the accountant is like the group of DCS programs in charge of related functions; the phone calls are like magic strings in your socket report(highlighted in my screeny) triggered by pre-defined events; the money in or out of corresponding accounts are like effects triggered by your report.

Thanks y2kiah for your timely correction. My appologies for making the confusion deeper instead of clearing things up. When I said executables I didn't really think of dlls which are also compiled functions to be executed. I'd vote for you on the lua file handling part. Finish them before running the program.

If you really want to stick to the board you have and achieve this, it's gonna require some programming which you may not like. Or you may get another type of card like those guys would suggest.

We may basically have unlimited variations on the top level, but the fundemental key may still be a couple of magic letters in the lua report.

Yes, Leo's board only works as DirectInput controls, if you don't see those in the axis control list in DCS options, then you can't assign them directly. lua exporting seems to be the only solution.

Adding one piece of info: In case someone started geting the sensation that the file export.lua itself is doing the communication, actually the DCS executable does. It reads whatever you've saved in the file and other files of its kind, then decides what to do accordingly. DCS executable implements a socket interface which may be addressed by its IP and port number. It's seen either by another PC on a network or another software on the same PC running DCS, depending on the IP you've specified in those lua files. There are numerous socket communication monitoring utilities that show you what the data looks like. Here's a screeny of data strings for a few simple instruments (the selected text). It requires some programming skills to translate that string into useful information. This is normally done by writing a custom software. And if this software has access to hardware, it can then redirect the data to any hardware it can reach.

Dude I'd love to see you get the pitch and roll motions working in that ADI. lol

Holy lord..... lol! hell yes

Hey it looks real cool. Keep it going. *Don't know how long my unblocking utility is gonna hold. lol

aww.... it's blocked in China. Not just hog pit, the whole fr***in' sites.google.com domain.

Looks good, got any dimensions?

Oh wow......:doh:

Good work! Hope there will be export.lua support for CDU text soon.

Since you're a student, if you're seriously considering building one all from scratch for yourself, you might need to do some homework including the following: Driving servos/stepper motors/other actuator alternatives for spinning your needles; Interfacing custom electronic devices with a computer through one of the following ports COM/LPT/USB/Ethernet. (COM and LPT are a lot easier to handle than the rest); Building a windows application software with a language you're most familiar with, add socket communication support and support for the interface you've chosen to connect with your device; A little bit of mechanics on calculating transmission ratios for gearboxes;

If the display component is soldered to the original PCB with metal pins, then it'd be relatively easier coz you've only need to design a smaller piggy back PCB to carry the component, and then stack it on the original PCB with flat cable or connectors. While if conductive rubber bars are used like what normally happens to segmented LCD's, then it would suck a lot.

I saw a whole bunch of lua files supposedly making up the framework of the CDU pages, it seems to be much less work just to export the text buffer through export.lua. 240 bytes or as much as 960 bytes will do the job. Despite this has been repeatedly asked in this forum countless times, there's no response from ED whatsoever.