Jump to content

smirkza

Members
  • Posts

    145
  • Joined

  • Last visited

Everything posted by smirkza

  1. My monitor is a 120hz nividia 3d ready one. I forget the exact model but when I get home will post it. Native res is the same as the rift. I run in extended mode. I only upgraded this week from a gtx570 and low value cpu. I had serious judders with that even with full low settings. The difference is remarkable. I'll be posting videos hopefully next week. Smirkza
  2. Just thought I would report in my findings - GTX980 I5 4670k Overclocked to 4.7Ghz 32gb DDR3 RAM 1600mghz I can run at full settings (minus cockpit shadows) and max distances without any nausea or juddering (that I notice, although no idea what fps is). It is simply amazing! Very much looking forward to trying it with EDGE. I'll be posting some videos and whatnot soon but for now I need to get back to the air! :pilotfly:
  3. That'll do nicely - Been waiting a long time to multi-crew with a friend (he doesn't like piloting but loves playing weps officer). Ta!
  4. :thumbup::thumbup: Can you expand on the functionality of this at all? ;)
  5. Really good interview about the future of stereoscopic vr across entertainment platforms. Worth a watch if for nothing else than seeing a red bull air race through a rift! I'm working in London this weekend might try and get down there to have a go myself...
  6. The seat has a built in giro that sorts that out, I think. Comes with software to figure position of rift in relation to seat instead of to the ground. Smirks
  7. Evening all... Just stumbled across this new project that should be launching on kickstarter soon. Has anyone else seen it? Looks like a great idea (wish I'd thought of it). Some rough cost estimates floated about have been below $1000! That's pretty decent compared to the other systems out there. Plus, this has the potential to be true 360' rotation in all three axis. Nice! Feel Three Motion Could be magnificent with DCS! :D:thumbsup: N.B. (Posted here not in the rift thread as there is talk of being able to mount a screen instead for those who don't want VR :joystick:) Smirks
  8. It's gonna be great! Can't wait! :thumbup:
  9. Hey Boltz, Ah, no problem at all. Whenever you get around to it, be great! I've seen in some threads (and after looking at the main export.lua within DCS itself that you can export things like radio frequencies, HSI and ADI bearings etc? Is that something A2DCS can assist with too do you think? Thanks again, Smirks
  10. So, I guess the next question is where do I find the ID for all of the lights & switches in DCS. All of the ones I have found in the past follow this sequence - 513 L_MAIN_FUEL_LOW 514 R_MAIN_FUEL_LOW But these differ from the config.xml entries? I'm just practicing making lights turn on and off, to get my head around how it all fits together, then I'll move on to switches etc.
  11. You, sir, are a legend! Top work! (Honestly, thank you - I've been pottering away with Arduino in the hopes of finally getting my head around how to connect it to DCS, then you came along and gave us this fantastic ap!) :thumbup::thumbup:
  12. Ugh, I see that I hadn't uncommented the device type in the config.xml I have now done that, and the Rx and Tx on the arduino flash away showing (I think) a good connection. However, the master caution light still doesn't flash. The two uncommented lines I now have are - <controllers> <!-- --> <add id="00" type="arduino uno" name="UFC Master Caution Panel" port="3" baud="9600" init="A2DCS[iD:0;DI:pin1,pin2;DO:pin1,pin2;AI:pin1,pin2;RE:pin1,pin2,0,2,-2;MI:row1,row2,col1,col2;]"/> </controllers> and... <outputs> <add key="UFC" value="O[0,1,13,v]" desc="UFC Master Caution Panel"/> --> </outputs> I'm sure I'm missing something here but I can't see what it is. Stumped and can't move forwards... Blast! Smirks
  13. Hi Boltz, Amazing work! I'm stuck somewhere between A2DCS extracting the info and it sending to my arduino. I am simply trying to have pin 13 flash in time with the master warning light. I have set up the config.xml file and A2DCS shows that it is receiving the info form DCS. However, my arduino just sits there,staring at me, not doing anything. Did I need to change the arduino sketch at all for it to pick up what I want it to do? My config file looks like this now - <?xml version="1.0" encoding="utf-8" ?> <A2DCS> <!-- serial port controllers --> <controllers> <!-- <add id="00" type="arduino uno" name="AHCP Panel" port="5" baud="9600" init="A2DCS[iD:0;DI:pin1,pin2;DO:pin1,pin2;AI:pin1,pin2;RE:pin1,pin2,0,2,-2;MI:row1,row2,col1,col2;]"/> --> </controllers> <profiles> <profile id="DCS World Warthog A-10C"> <inputs> <!-- input definitions from arduino controllers key : arduino input string for processing formatted I[controller id, control id,,, value] value : input string sent to dcs world for processing desc : textual description of input --> <!-- an example of simple switch input events: <add key="I[0,D2,0]" value="123,0" desc="AHCP Panel.Master Train"/> <add key="I[0,D2,1]" value="123,1" desc="AHCP Panel.Master Safe"/> <add key="I[0,M1,1,1]" value="124,1" desc="Matrix 1, Switch 1, Value 1 mapped to DCSWorld Command 124 Args 1"/> --> </inputs> <outputs> <!-- output definitions from dcs world key : acronym for the output as specified in dcs world arduino.lua script value : output string sent to the arduino for processing formatted O[controller id, output type, pin configuration,,, value] desc : textual description of output --> <add key="UFC" value="O[0,1,13,v]" desc="UFC Master Caution Panel"/> <!-- an example of a single led output on arduino pin 13: <add key="UFC" value="O[0,1,13,v]" desc="UFC Master Caution Panel"/> an exmaple of a matrix led output on arduino pins 6, 7 and 8: <add key="WLP" value="O[1,2,6,7,8,v]" desc="Warning Light Panel"/> --> </outputs> <interps> <!-- polynomial spline interpolations used by input devices such as potentiometers key : key of input device comprising controller id, pin id value : dcs world command and value arguement definition mask : output mask to apply to splined value interp : pin min, output min, pin max, output max min : absolute minimum output value max : absolute maximum output value desc : textual description of interpolation --> <!-- an example: <add key="0,A0" value="123,v" mask="0.000000" interp="0,0;1023,1" min="0" max="1" desc="Analog Input Interpolation Curve - Potentiometer"/> --> </interps> </profile> </profiles> </A2DCS> Thanks for any help you can give, Smirks
  14. I've tried that before and not been able to get it to work. I'll give it another go, but... Happy to say I've gone through DC's thread 3 x and on the last go I've managed to get the caution light to work! It's such a small thing, but it opens so many doors! Thanks to everyone who puts the work in the help out us coding illiterate dreamers! :thumbup:
  15. Superb, thanks TigerShark! I'm actually going through his forum post now (only just found it) although I've reached a stumbling block when trying his shortened caution light blinky. Getting errors galore when trying to change things as he suggest... This is bugging me as I can handle the arduino fine, but it's all the PC based stuff that's getting to me. If only there was a simple, stand alone program that sent data out to arduinos for you, life would be great! Back to the testing! :thumbup:
  16. Hey TigersharkBAS - great work so far! I have a quick question for you reguarding the wiki post you made here - Connecting DCS to Arduino I have gone through all of the steps (even copied and pasted the code from the updated version like you said o at the bottom, but I keep getting an error when trying to connect to DCS. (The test harness worked fine and connected to Arduino). The error that comes up is - System.ArgumentOutOfRangeException: startIndex cannot be larger than length of string. Parameter name: startIndex at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy) at System.String.Substring(Int32 startIndex) at UDPBridge.Form1.ProcessData(String data) in c:\Users\shaun\Documents\Visual Studio 2013\Projects\UDPBridge\UDPBridge\Form1.cs:line 119 at UDPBridge.Form1.buttonUDPON_Click(Object sender, EventArgs e) in c:\Users\shaun\Documents\Visual Studio 2013\Projects\UDPBridge\UDPBridge\Form1.cs:line 46 Any ideas on how I can fix this? :cry: Cheers! Smirks PS - Here is my UDP code (copied straight fro the github post) using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Linq; using System.Text; using System.Threading.Tasks; using System.Windows.Forms; using System.Net; using System.Net.Sockets; using System.IO.Ports; using System.Threading; namespace UDPBridge { public partial class Form1 : Form { private bool done = true; private int listenPort = 65002; public Form1() { InitializeComponent(); } private void buttonUDPON_Click(object sender, EventArgs e) { done = false; UdpClient listener = new UdpClient(listenPort); IPEndPoint groupEP = new IPEndPoint(IPAddress.Any, listenPort); string received_data; byte[] receive_byte_array; try { while (!done) { receive_byte_array = listener.Receive(ref groupEP); received_data = Encoding.ASCII.GetString(receive_byte_array, 0, receive_byte_array.Length); if (received_data.Length > 0) textBox1.Text = ""; string[] r = received_data.Split(':'); foreach (string s in r) { ProcessData(s); textBox1.Text += s + Environment.NewLine; } Application.DoEvents(); Thread.Sleep(500); } } catch (Exception ex) { textBox1.AppendText(ex.ToString()); } listener.Close(); } private void buttonUDPOFF_Click(object sender, EventArgs e) { done = true; } private void buttonCOMON_Click(object sender, EventArgs e) { string[] ports = SerialPort.GetPortNames(); string query = "*9999-0#"; foreach (string port in ports) { SerialPort p = new SerialPort(); p.BaudRate = 9600; p.PortName = port; try { p.Open(); if (p.IsOpen) { p.Write(query); string s; Thread.Sleep(500); s = p.ReadExisting(); p.Close(); try { if (s.Contains("<ident:")) { int i = s.IndexOf("<ident:"); s = s.Substring(i + 7); i = s.IndexOf(">"); s = s.Substring(0, i); if (s == "BORIS") { serialPort1.PortName = port; serialPort1.Open(); } } } catch { } } } catch (Exception ex) { ; } } } private void buttonCOMOFF_Click(object sender, EventArgs e) { if (serialPort1.IsOpen) serialPort1.Close(); } private void ProcessData(string data) { data = data.Substring(9); string[] d2 = data.Split('='); if (d2.Length != 2) return; if (d2[1].Substring(d2[1].Length - 1) == "\n") d2[1] = d2[1].Substring(0, d2[1].Length - 1); switch (d2[0]) { //Master Caution Switch case "404": SendSerialData("404", d2[1].ToString()); break; default: break; } } private void SendSerialData(string function, string value) { if (serialPort1.IsOpen) { string sendthis = "*" + function + "-" + value + "#"; char[] c = sendthis.ToCharArray(); serialPort1.Write(c, 0, c.Length); } } } }
  17. I'm not planning on using the castAr to display any guages, MCFD or the like. Instead, I want a full simpit with working gauges as per current setups. Then around this I will build a reflective dome. SO, the castAR will simply be projecting the outside world whilst all cockpit type stuff is done in my simpit. I think it's the perfect fusion, and I can't wait to find out if it works. It should do, as Jerry et al from castAr have been working with the guys from Oculus (pre-FB purchase anyhow) to ensure all VR/AR systems work the same way. Only time will tell I guess... :thumbup:
  18. I too am keen for this to work with DCS. I'm planning on a full cockpit surrounded by a reflective dome. Full sim AR - will be great (if it works!) :thumbup:
  19. After going through Helios properly for the first time I think all of these are available for extraction. Now I just need to figure out how to communicate with an arduino. All of the guides assume a level of knowledge I don't yet have (not got a programming background and never extracted data from DCS before).
  20. Are the HSI values also included in this? Potential values and inputs are - - Power OFF Flag - Compass Card - Range Indicator - Bearing Pointer 1 - Bearing Pointer 2 - Heading Set Knob - Heading Marker - Bearing Validity Flag - Course Set Knob - Course Selector Window - Course Arrow - Course Deviation Indicator (CDI) - To-From Indicator Thanks in advance! Smirks
  21. Cool glad you got it working :pilotfly::thumbup:
  22. Make sure your space bar is set to "fire" (I think it's "fire", it says at the start of the tutorial anyhow).
  23. There is of course the third answer that takes elements of both concepts and combines them - real life pit and a projected display - The CastAR headset out later this year. It just seems the perfect symbiosis between the love of creating/flying custom pits and the need for a working display to go with it. Yes, it does still lack peripheral vision, but combine with a second headsets projectors to increase FOV and you might be on to a winner. Plus, it's going to be cheap as chips! (kinda) That said, I have no idea of viability until a developers kit comes out to test properly. It might not work at all :music_whistling:
  24. Aye, I was wondering about the fingers too. I don't want to hold a controller, I want to go from holding my HOTAS then be able to reach out with either hand and just flick the switch. This is where we will need an avatar of some kind in game with both arms functional, or at least 2 'pointers' to allow either hand to work (save reaching across to the left panel with the right hand or vice versa). Also, I think this is possibly better than the omni - http://www.dvice.com/2013-9-25/virtualizer-vr-treadmill-gives-virtuix-omni-run-its-money For one it allows vertical movement to be taken in to account (crouching through to jumping). Plus, it allows you to sit in the device which will be great for things like ARMA et al. The next couple of years are gonna be pretty damn great!
  25. Well, this might prove to be an answer to the 'operate the virtual cockpit' problem - https://www.kickstarter.com/projects/yeitechnology/priovr-suit-up-game-on Still having the ability to use a HOTAS system will be important, as will (crucially for me at least) seeing an avatar in game reaching for the dials as you do to allow for proper placement of fingers and hitting the right switchl. Something more than just seeing a floating cross anyways...
×
×
  • Create New...