donbinator

I've been having the same problem for years actually. On two different PC's. I have an A-10C cockpit which I had this problem years ago when the F-18 module first came out (I was trying to wedge settings into my A-10 so I could fly the F-18). Now I'm having it on my "development" PC where I write code to interface with DCS. Pressing the Axis Assign button does absolutely nothing. I've tried re-installing DCS, re-installing .net. Basically I'm sitting here with DCS saying "NO WHEEL BRAKES FOR YOU!!!". I'm on a completely different version of DCS than I was 4 years ago, and I'm running latest stable at the moment, not beta.

Huh, doesn't work with 2.5.0 either anymore. I haven't changed the setting in so long that I have no idea when it broke. Gotta assume it's something wrong with the large number of HID drivers I have for my cockpit??? Not really sure where to go from here. Really really really want to fly an F-18 :(.

reinstalling didn't work, going to try repair/reinstall of .net 3.5... This time I didn't even download any modules. just tried to set rudder to my rudder pedals in general. I First cleared all categories though.

I'll try reinstalling DCS world. There's definitely something wrong. If I set to defaults my rudder pedals work correctly, and I can see the bar go left and right as I move them. If I clear that axis, and try to reassign it, nothing happens when I click the axis assign button. The button itself goes active and inactive when I press and release it, but there is otherwise no indicator that anything has happened, and inputting my rudder pedals at that point does nothing as well. This stands true for configuring the A-10C as well as the F-18C. I have yet to see that button do anything in the open beta. Some binding in .net must have gone wonky or something. I did try rebooting as well which didn't help.

isn't a pop up supposed to display indicating it's waiting for an axis input when you press the button?

I cleared all of my axis bindings except my trackir which is working correctly.

Just downloaded open beta 2.5.2 and F-18. I can't get the Axis assign button to do anything. Nothing happens when I click it and my axis aren't be assigned. My axis do work (if I use defaults I can see them moving back and forth) but defaults aren't right for my cockpit. Any suggestions? I don't have throttle and moving my rudder pedals does all kinds of strange stuff with default settings.

Yep that worked! OK except for my radar RDR thingy but that always gets screwed up so I have a backup for that. Thanks again, not sure how whoever figured this out did, but that would have taken me forever to figure out!

Thanks JG14! I actually fly quite frequently, but I try to avoid grabbing every single update since I usually have a spare 40 minutes or so to fly, and I find the updates take all my flying time :). Usually the updates haven't messed with my export so I was surprised not to see more people asking about this one... Thanks again!

I rarely start a thread on the DCS forum but I'm a bit stumped. It appears that export.lua moved again? It used to be the dcs programs folder, then moved to the saved games folder, now there seems to be one again in the scripts folder. My helios profile, which has been working for years, is not now, nor is my custom stuff for all my switches and knobs etc. I have no idea what version I just installed, but it was 1/4/2017 when I installed it (an upgrade to the 1.X series DCS). The new export.lua in my scripts folder looks like it has a lot of new helpful comments, but I used to be able to click a button in my Helios config and it would modify it for me... No one has said anything so I feel like I'm missing something basic here...

Just to be clear though, the Rift DK2 is a *blast* to play with. It's not ready to be a hard core flight sim tool, but man it's fun to put on and just walk around in a haunted house. I seriously can't play "Affected" for more than about 2 minutes before *$&% gets real and I have to whip the display off my head. My 12 yr old son and I have a contest going on to see who can last the longest without removing the head set. You really have to try it to believe what a difference the peripheral vision makes to ones sense of immersion. I think that alone is kind of the point of this product at this phase. It's to say "hey look at what the future of entertainment is going to be like". I can't even *imagine* what the horror movie folks are going to do with this in the future...well actually I can, picture a google map van like view of a horror movie, where instead of looking where the director wants you to look, you can look all around you like you are in the movie. I think most people would run screaming from a decently recording movie script...

Oculus Rift DK2 review with DCS Hey all, just got a Oculus Rift DK2 for xmas (awesome wife!) and thought I'd give my impressions so far of using it in my cockpit. It's wonky to set up because I have two video cards and it doesn't seem to like that. To get it to work I have to make the DK2 my primary monitor, then turn it off so I can see again (main monitor becomes primary). Then I start DCS World and make sure "auto detect Rift" is checked. I start the mission and while it's loading turn on the rift. This puts me in a kind of a weird position in the cockpit so I hit "5" to reset my position. Flying around is pretty amazing. The immersion is what's impressive. I'm used to using to my IR tracker so while I used to be able to see 360 deg by just turning my head a little, I now have a realistic range of motion. To look back over my shoulder at my wing man I have to *look back over my shoulder*! The immersion is so intense that motion sickness is a real problem. When banking left or right my stomach turns when the aircraft banks but my inner ear doesn't feel it. I'm sure one could get used to it much like real pilots have to get used to motion sickness for other reasons. I have NVidia Geforce 660ti graphics cards with i5 processor and 16 gigs of RAM. Even with that there is enough jidder that it adds a bit the motion sickness and detracts a bit from the immersion. Suspension of disbelief is ruined slightly by jidder, but certainly not completely :). The graphics are the real problem. The resolution just isn't there yet for this type of gaming. I can't really read any text unless I get really close to it (no chance of reading the text for outside world markers on red/blue units). I can't even see the targets until I get really close. This aspect of the DK2 still baffles me. 1994 is calling and they want their VirtualIO I-GLasses back. Why can't they just take two cell phone screens and stick them in there? In summary: This is *definitely* the future of gaming, including flight sims. All immersion gaming will be using something like this. My kids won't stop bugging me just to play the "swim around like you are a scuba diver" game. It really is a totally different experience. The DK2 in my mind is nothing more than a demonstration of better peripheral vision and head tracking than any other affordable platform has demonstrated, and the power of immersion for gaming (and of course other applications, but I'm just looking at this from a gaming perspective). Otherwise I'm really not seeing any new technology here. First person to put good resolution on a platform that supports the frame-rates needed wins. Oh, and combine that with a Kinect like interface (which I believe people have already done, haven't tried it yet on my Xbox) to track your body movements and insert them into the VR. It really is a strange feeling to hold your hand up in front of your face and not see it. Anyways, I'm having a lot of fun with it, but it's not replacing my cockpit project anytime soon :).

Yeah my RWR and CDU (or whatever you call the computer screen thingy) worked and then suddenly didn't. Thanks for the lesson. Was this changed in a recent update?

Ah!!! There's the missing piece if info. I didn't know that windows is buffering all udp traffic. I'll have to look that up...thanks!

Yes I know UDP is connectionless. Let me use your lua as an example to what I think is my problem, you are welcome to correct me if I'm wrong. Here you are setting the timeout for the listener to 1mS. CMSPExport.listenconn:settimeout(0.001) This means that the listener will listen on port 7778 (CMSPExport.listenconn:setsockname("*", 7778)) for 1mS, then return if it hasn't received anything. It also means that if you don't send your packet from your program in that particular mS of time, your lua script won't receive it. That's my problem. It's a broadcast to 127.0.0.1 on that port for whoever is listening, and if no one is listening at that particular time the packet is lost. Obviously yours works, how?! That's my question :huh:. My guess is that unless there's something I don't understand about sockets, the mS that your listener is listening is actually a large percentage of the round-robin timing of your system, that is, 1mS is spent listening, and 1.1mS is the period, so you have a good chance of an active listener when you send your packet. If that's true I want to find another way to do it because that's going to be unreliable...I think?