brydling

Please delete this thread. I will ask in another forum section.

Hi, I am planning to buy an LCD-screen for the ABRIS and a CRT-monitor for the Shkval. What are the sizes of the real things? A guess about the ABRIS is 10.2" 16:9-format? /Niclas

You're absolutely right. However, BS is a helicopter simulation and that makes my only flight simulator-interested friend not wanting to buy it. Without multiplayer, one dimension is lost. I don't feel that I have the time to be active in a squad.

Having a realistic flight environment comes first. I haven't flown enough to be aware of these shortcomings, hope they get fixed really soon. After all the only flyable aircraft's main tactic is to hide behind terrain. That would be awesome. Although I'd rather see a multi-purpose aircraft to build a simpit around and be able to fly all kinds of missions, the Su-25 is still on my wishlist.

Yeah, the dynamic campaign is what really makes it worth flying the game. If only we could have that in DCS. The feeling of knowing that my success or failure makes a difference in a realistic way is half of the fun. But I can't wait to get my hands on DCS Warthog and TM's upcoming A-10C controller replica either. :joystick:

Very true. I already am an Area 51-member for Fighter Ops and I bought Black Shark the moment it got out. I will of course buy DCS: Warthog when it gets available too. I just need something to do in the meantime, when I can't fly Falcon because of NVIDIA-card issues and my friend doesn't like helicopters ;)

Ok, thanks for straighten that out for me! As far as aircraft systems goes, one of the Falcon-variants are still the best the fixed-wing market has to offer?

Hi, How far from DCS-standard is the Su-25T of Flaming Cliffs 2? I want a high-fidelity fixed-wing simulator and don't know which one to get.

The point with the modified card is that it will still work with SIOC, otherwise I would have made my own servo card that also included a serial number so that it didn't rely on the way Windows names the cards. With opencockpits solutions you have to change in the config-files if you for example move a card to another USB-port or if Windows for some other reason decides to change the identification string, because the cards doesn't have any other way to identify themselves. Extremely annoying when you notice that the instruments are not working anymore and after 30 min of testing the usual SIOC-maintenance things (reload code, restart SIOC, restart computer etc.) find out that Windows decided to change the name of the card so that you have to change all the references in the SIOC code. But in the absence of other I/O-solutions with scripting capability, it's nice if the card works with SIOC. Edit: The exact timings of the stock cards are from 0,25 ms to 2,5 ms. A Futaba S3003 uses 0,4 ms to 2,5 ms. The result is that the servos doesn't move when you write lower values than 100 to the servo cards. With a total span of 0 - 1023, the mod should yield almost 11% of resolution improvement. Edit: I have started blogging about my development now. I don't feel that this belongs in your thread, so check out brydling.blogdns.com instead and message me if you are interested. I will make a clone of the stepper card too, since these cards REALLY suck.

I am planning on programming a PIC18F2550 to replace the 16C745 on the servo cards and use it to output a pulse that goes from 1.0 ms - 2.0 ms instead of the almost 0.0 ms - 2.0 ms interval on the stock version. The crystal will have to be replaced too, but that's an easy job. Sounds interesting?

Thanks!

Merry Christmas! I hope santa will bring you good joysticks and simpit-equipment!

He means that you can build your own CNC-machine for $100 :-)

I am awfully jealous on that machine! Hope you will get a good result with the OpenCockpits cards. The update-rate are far from perfect in our simulators, but it could be due to SIOC running on a different computer and talking to FSX over WideFS. One thing to think about regarding the servo cards is that they output a pulse that goes from almost 0 ms up to 2 ms in width. That menas that a lot of the available resolution is lost in a region that most servos can't use. See if you can find out what pulse-widths the servos use before buying, or else you can forget about that 10-bit resolution because most servos use a pulse-width from 1 ms for one direction to 2 ms for the other direction.

Nice movie! I can't wait until I will make my first panel/instrument :) Do you fly with the cockpit visible on the visulator?

Excellent work Oakes, absolutely amazing. I am an electronics student in Gävle and are planning on starting a similar project myself. I am a part of the NovelAir team, if you know what that is. We build simulators out of a cut-off J35J Draken cockpit and an AJS37 Viggen. My biggest problem is that I really hate SIOC and the OpenCockpits solutions, so I'm going to have to develop my own interface cards. I could easily make some cards for inputs/outputs, motor control, servo control etc and write PC software for them that are specific for DCS: Black Shark, but I want it to be as generic as possible so others can use it (NovelAir for example) and therefore I have to create a program with scripting capabilities like SIOC. This is the main obstacle, and with all the software and interfaces I do for NovelAir and my own studies it's a little hard to get the thumb out of my ass and start designing such a complex interface system. Right now I am designing my own joystick card, since I don't need any PC software and scripting capabilities for that. The rest will have to wait.. Maybe until next year after I have taken my graduation and got myself a job. If you want, PM me or add me on MSN. I think we can have a lot to discuss ;)