Bullant

If it were an exact functional replica of the F18 throttle? Yes I would.

Yes. To start with.

2 weeks lol I live in GMT+10 and Wednesday updates are usually available by lunchtime Wednesday, so that makes it around 0200Z. I guess it depends how many times the servers fall over before they stay up long enough for people to start seeding the whole thing ;)

Can't believe nobody has pointed out the best bit of this video!! The beach volleyball courts at 0:20 lol

Solved it! Not sure which of the two changes I made fixed it (I know, I know), but I disabled MSI afterburner and I opted in to the SteamVR beta and now it works.

It's interesting that you say that, because I don't seem to be able to get it to display on my monitor. Or if I do then steamVR is also there (it depends on what I have set as my 'main display'). So I either get the VR/split screen display OR I get the non-VR 2D display. But always on EITHER the monitor or the PSVR. I can't seem to get one on each, which is obviously where my problem is coming from.

Thanks mate, I think that option might be ticked but only out of complete frustration when it wasn't working with it ticked! Will try unticking and see how I go. I have a vague feeling that the problem might be down to me running a 3 monitor setup. I have two of them turned off, but the one connected via DP still shows up as a (disabled) display. I'd disconnect the cable, but it is one of the stupid one with 'hooks' and I can't get the dammed thing out! Winning, pulling the power cable from the monitor made the display drop out. However ... still not great. Turned off the hand controllers option. Have Trinus setup to put the VR display on display 2 (the PSVR). And it seems to do that, as long as I have display 2 set as my main display. But I still can't use the mouse or keyboard while in VR mode. If I tab out so I get a horrible double image on the PSVR I can select menus, just, and even managed to make it back into the plane sitting on the deck ready to takeoff ... in proper VR view by clicking on the red background ... but it was completely refusing to take any of my inputs from mouse, keyboard or HOTAS.

Let's make this a simpler question. Am I supposed to be able to use the mouse to drive the main menu when running in VR mode. Because at the moment I can get the main menu page up, I'm in the hangar can look around at the cool jet and see the menu in front of me. And I have a white dot that I can move around. But I can't click on anything. This is with the PSVR (display 2) set as the main display. If I set my monitor (display 1) as the main display and much around with alt-tab I can get a compressed view of the menu in the middle of the screen and I can move the white dot and select menus ... but the headset shows nothing but the display 2 desktop.

One small win, setting the second display to be the "main window" makes the split screen run on the psvr properly and both steamvr games and dcs start up properly. But I still can't find any way to actually select a menu item so I can launch a mission. The white dot moves with the mouse but I can't seem to make it select anything ...

Hey guys, Hoping someone else might have run into the same problem. I've installed and configured Trinus. The PSVR is being recognised as a second monitor. I have my main monitor set to 1920x1080. If I run any SteamVR game I get pretty much the same results. The double image comes up on my main monitor and I see the second desktop in the PSVR. If I set the monitors to duplicate I can see the proper VR image in the PSVR but I can't get any controls to be recognised in game. For instance in DCS I can see the dot on the menu and can move it with the mouse but can't click. In DCS, if I alt-tab I see the double red eye image in the background and single DCS in the middle of the screen. And the mouse works. But I have no image in the PSVR. I saw a suggestion of hitting alt-enter from this point, but this leaves me with a menu that I can select but a fixed, non-moving, non-VR display in the PSVR. Thoughts? Other than go and buy a made for windows VR headset lol. Edit: I am using the standalone version of DCS, but I believe it should work fine, from what I have read.

Thanks guys, it's weird uno as slave works, mega on the exact same 487 chips doesn't work. Away for work at the moment but will re-attack on the weekend.

I am pretty much at my wits end here. I have a UFC that has a mega behind it. I have a switchbox that has a uno behind it. Both work perfectly connected direct to the PC via USB. I have a second mega configured as a master and hooked up through two 487MAX chips on a breadboard. If I modify the sketch for the switchbox and hook it up it works fine. If I do exactly the same thing for the UFC nothing happens. In both cases I am using the same wiring on the slave DI -> TX0 (D1) RO -> RX0 (D0) DE/RE -> D2 I have a third mega that I hooked up and wrote a very simple sketch to hook up the internal led to the master caution. I swear this worked once, but not since. I noticed on my maser that the RX led flashes rapidly and continuously, but not the TX led which does not appear to do anything. Is this normal? Any other suggestions? Because at this stage I am looking at just running a second usb cable for the USB, or rewiring it to use multiple unos ...

Weird, tried again with a brand new clean mega as the slave and a very simple sketch turning on the LED tied to pin 13 with the master caution. Worked perfectly ... then stopped. The slave 487 chip was super hot ... swapped it out and now it's not working at all again. Could be a problem with my breadboard, will investigate further when I have more time.

LOVE it!

Thanks for the tip, but I swapped out the mega for a Uno with exactly the same 487s setup on the breadboard and it worked fine. So had to be something weird with the mega.

I had the same problem. Cura 3.5.1 opens it an automatically scales it correctly. Go figure.

You need to either find a rotary that has a pull function or work something out to approximate the functionality. Looking at this though I see that I have missed the functionality in dcsbios to capture the pull motion, I will look at adding this shortly.

I was thinking the same thing, the lettering is much deeper than what I got off my printer.

Cheers mate, still waiting for a chance to have another go with mine, must have had something wired up wrong.

Thanks, appreciate the effort. Must be an issue on my end, will try again.

That is probably more of a general dcsbios question than specific to the F18 module.

No idea, that's someone taking my code and rehosting it. Only guarantee is to get the latest version from the first post in this thread.

I'm finally getting around to converting to an RS485 setup, and my test with a mega as master and uno as slave went well. However, my UFC has a LOT of input requirements and is currently running on a mega. Any attempt to run a mega as a slave is resulting in absolutely nothing happening. I have the TX/RX wires running to D0/D1 just like the UNO. So can someone confirm if it is actually possible to use a mega as a slave?

This! Once I figured this out, landings became "easy". "Easy" because flying the pattern correctly still takes a lot of work, but knowing that all you really need to worry about is power for descent rate makes things MUCH easier. Also, I read somewhere to hold off dropping flaps until you hit 190 knots. This has made my pattern much smoother. Full disclosure: I have probably spent upwards of 20 hours just doing airfield landings in the hornet ... now that they are acceptable I'm starting on the carrier and its a whole new ballgame lol.

You are welcome, the more people that use it the happier I am :) Nope, the module just doesn't expose the inputs/outputs in the same way as every other module.