Mr.Fenestron

I'm looking forward to seeing the progress on your build as well DM. Keep us posted :)

I was aware of Vulcan but I thought that was an ATI(AMD) product and even if it is open, the top selling, best performing company has no rational basis for abonding it's costly R&D of proprietary API's (nVidia). Love them or hate them, nVidia provides the fastest and best performing graphics acceleration products on the market. This is not a question of cost per Fps% because VR requires the best. Being the first time market with Feature 'X' does not guranteed a company will remain in the lead, this is only acheived through continuous innovation. My slight nod to single core processing is less important to my point than VR itself. I meant it such as, if they are already going to rewrite the engine, might as well add multi-core processing to the to-do list. Once again, I do not assert this is an easy task, merely a necessary one. Reviews of VR HMD use in games are mixed and not representative of the simulation market space because of their implentation standard differences and usage scenarios. An FPS game, to be immersive, requires far different hardware than a flying/driving simulation even though less components might be necessary. An example of best case immersive scenario: replica cockpit with VR vs a walking/running platform that allows you to also jump & crawl with lifelike autonomy and the "guns" to pair with the VR platform as well. It is the addition of complex movement hardware and expectations of the VR platform as a whole that creates the disparity in VR expectations. As a VR user I can tell you, I am always chasing after the immersion factor and everyone who has used my setup, most never having used VR before, understand the alure to VR with regard to flight simulation. VR is growing in popularity because the hardware is getting better. Many have used the Oculus/Vive but the PiMax 5k+ is a tremendous leap forward. It still isn't perfect but I can read the gauges just fine now and the screen door affect is substantially less detracting from the experience overall. If there is a reasonable valid reason why ED chooses not to use Nvidias API's so be it but I hope it is a carefully made decision and not done for proprietary reasons because as I said, nVidia is the best, that is just a fact and that has been so for quite a while. This is why SLIVR under the SLIWorks software provided by nVidia would benefit most VR users. SLI is dead, we all achnowledge that, but VRSLI is new and just starting to get adopted. There really is no valid argument that I can muster why everyone here would not be onboard with support for the APIs, regardless of if ED would actually go for it. They are a company and they make $ and decisions based on Demand. If we demand it, they might do it, business wise that's a pretty straight forward statement, wouldn't you all agree? Here is where my ignorance prevails though. Can ED implement both APIs for Vulcan and Nvidias VRSLI? This way you can use whichever companie's hardware/software you want? I would assume we all want a more immersive experience, isn't that the point of a "simulation"? VR is the way to go. If you disagree, I strongly urge you to give VR a try on a PiMax 5k+/8K with a 1080TI / 2080TI if you are able. I would wager you change your mind pretty darn fast... If I am wrong in my initial assertion that this is an ED problem and can be mitigated through the use of Vulcan I would be ecstatic. I will be doing further research in the meantime.

To clarify, I do NOT mean using SLI with VR, I mean VRSLI, which uses each gpu to render each eye. Has anyone heard any rumblings with regard to the implementation of VRSLI in DCS or is this another "single core permanent limitation" kinda deal? The PiMax 5k+/8K is pretty darn impressive with regard to FOV, Screen door affect, and clarify; and rending each eye with a dedicated 2080TI would be pretty darn awesome! IMHO, if it cannot be supported, a rewrite of the engine would be highly preferable. I in no ware assert that this would be an "easy" or "quick" task but that does not mean it isn't necessary. The majority of simulations will be done using VR in the near future and continuing to build upon a platform that does not support it (along with multi-core processing) would be costly for ED in the long run because another company will provide the support. Mass VR adoption is only a matter of time, and that time is fast approaching...

Ah, he beat me to it.

I'll measure it tonight. I have an A model but there should be no difference in the measurements you want.

By linear do you mean without the measure of the arc?

Do you plan to add any more knobs/buttons to shapeways, I dont see buttons for the UFC or CDU? You still get kickback for shapeways right?

Bummer. Do you happen to have a list of which items and how many I should buy? Also, do you know of the knobs you dont offer are easily obtainable?

Shapeway it is then. I could have sworn you had a pacage on your shapeways for an entire A10 cockpit kit or am I mistaken?

Hmmm, thanks Hans. Perhaps I should write my own then... As silly as it sounds, I was hoping ED provided a drag and drop tool like Helios to make it easy for us

Would a full complete cockpit order be sufficiant to make your resin knobs? (And how much if so). Ya, I figured I would have to have 3 Masters, I just wondered if maybe I could do it all with just 1 Master. I found a handy article on the 485 https://github.com/Gadroc/dcs-bios-arduino/wiki/RS-485-Protocol

No, I just have my A model throttle. When you setup a single master board with multiple slave boards, such as with a Mega (54 digital I/O), how does each slave board wire into the host? I read that you used real knob casts to make yours but I also seem to remember you not liking 3D printers as much for accuracy problems. Are your shapeways knobs as accurate as the real deal?

What do you think of this one? http://www.newwoodworker.com/reviews/jnsndigprotactor.html . Its accurate but I worry it may be a bit too bulky to get int those hard to measure spaces... Any particular function of protractor/calipers you recommend?

Well thats a bummer that you got burned like that. Our entire community would have benefited from a book like that. If you don't mind me asking, how do you go about getting those accurate measurements from your panels? Do you use a digital protractor and digital calipers?

I was thinking of using the BareDuino Nano (8 Analog, 14 Digital I/O) for some of the less complex panels. The little Arduino board is compact and only cost about $10. It's a real shame all of your images went down since the image hosting website went screwy. Any chance you would repost all of your pictures in a single collect? Its a sad day when so much knowledge is lost and your thread is a goldmine of knowledge. I was rereading the entire thread when I came across some situation where you were going to develop a book, did anything come from that? By the way are you still selling stuff on Shapeway?