lt.shifty

Thanks Vinc, I figured that might be the case for the slave, I'll try powering both Arduinos with an external PSU and see if that kicks it in to life. I have got DCS Bios working with a single Arduino (nano, pro micro and mega all working fine standalone. *I'm aware pro micro doesn't work for rs485 with dcs-bios). I did a bit more fiddling with the multimeter last night, and I noticed the 5v out from the nano is only 4v, guessing that's because it's currently powered by USB? Or just a bad Chinese clone? I've tried swapping the Rx/tx on the master, and using all of the Rx/tx pins and with each way around. Pretty sure now though it's because I'm using USB to power the nano.

nullCan anyone help me please. I've been trying for a couple weeks to get this circuit working and just can't for the life of me. I've attached pics of my circuit, it's wired exactly the same as the diagram on the OP. And I'm using these MAX487CPA chips. I've basically tried replacing every part, so I've ruled out faulty components. I've tried powering the slave Arduino (Nano) (master is a mega 2560) using an external 12v power supply, or as shown in the pic via USB (using a phone charger) because I wondered if using USB to the PC was causing the RX/TX lines to get tied up and unavailable to the nano for RS485. I've checked the datasheet for the chips, although this is a guess tbh who knows from AliExpress, and I'm sure I'm using the correct pins. I've also switched to the Skunkworks DCS-BIOS fork as that was suggested in this thread. I've also verified with a multi-meter that all connections are fine. I do notice that when the A-B lines are attached, the led on the nano is constantly flashing very quickly, so it's like there is something transferring data. Serial Monitor on the Mega doesn't show anything. Edit1) Added a screenshot of what DCS-BIOS Serial shows with DCS running, this doesn't appear to change if I disconnect the slave.null Sketches for reference: Master: /* Tell DCS-BIOS this is a RS-485 Master. You will need to flash this to a Mega 2560. */ #define DCSBIOS_RS485_MASTER /* Define where the TX_ENABLE signals are connected. You can connect up to three half-duplex RS-485 transceivers. Arduino Pin RS-485 Transceiver Pin TXn ------------------- DI (driver input) RXn ------------------- RO (Receiver Output) UARTn_TXENABLE_PIN ---- /RE, DE (active low receiver enable, driver enable) If you have less than three transceivers connected, comment out the corresponding #define UARTn_TEXENABLE_PIN lines for receivers that are not present. */ #define UART1_TXENABLE_PIN 2 //#define UART2_TXENABLE_PIN 3 //#define UART3_TXENABLE_PIN 4 #include "DcsBios.h" void setup() { DcsBios::setup(); } void loop() { DcsBios::loop(); } /* The following #define tells DCS-BIOS that this is a RS-485 slave device. It also sets the address of this slave device. The slave address should be between 1 and 126 and must be unique among all devices on the same bus. */ #define DCSBIOS_RS485_SLAVE 1 /* The Arduino pin that is connected to the /RE and DE pins on the RS-485 transceiver. */ #define TXENABLE_PIN 2 #include "DcsBios.h" DcsBios::Switch2Pos engContSw("ENG_CONT_SW", 3); void setup() { DcsBios::setup(); } void loop() { DcsBios::loop(); } null

Next question, does any of the above work with MT?

How did you get 2.8? Still no update for me even with trying to call dcs_updater with the 2.8 branch

Is this still a valid mod for the latest versions of DCS? And will it work with PimaxXR runtime?

Yea found that said online a lot, I've dropped my speed down to 2800 and it's made next to no difference in any game, maybe ~4fps at most.

Thanks dude, Guessing it can just boot directly into a game then, no launching an app like on the Quest 2?

Turns out my X370 board (Hero VI) just doesn't take 64GB of RAM at 3200Mhz. Managed to get it running at 3000Mhz 1.4v with 20-18-18-36 timings. Not great, but I'll bag an X570 board when pennies allow.

Getting fed up of all the issues with the Quest 2, so looking at the Valve index to tie me over until I can get my hands on the pimax 12k next year. Does anybody know if I actually need the controllers? I have no intention of using them in game, but on the quest I have to use them to launch quest link, does the index have the same startup process? Or is it just turn it on, and go? Last thing, does the index work with standalone version? Cheers

I'm running on the crosshair VI Hero X370. Did just run into an issue today though, added an additional 32GB of ram (now 64GB total), and getting memory errors. Hopefully just a tweak in voltage needed or something, and not days of testing and an RMA.

Okay so update time, I went with the 5800X3D. Just saw your suggestion @BitMasterwhen coming to update, but absolutely right this CPU is seriously good. Now running the game with all settings at max, 2x AA, pretty much and a PD of 1.5. I put it to that for a laugh just to see if it did have that much punch, it does. Still struggle with the AH64 on Mariana's, but who doesn't. Dropping PD down to 1.3 resolves that issue though, bare in mind I have forest details and distance up to max here. Getting a min FPS of 45 now and it Avg's around 60, peak 90. Once I'm home from work I'll update this thread with full settings and rig spec for anyone else coming across this thread.

Anyone know if an upgrade from a Ryzen 3600 to a 5900x will yield any benefits in DCS? Current rig: GPU: 3080ti CPU: Ryzen 3600 RAM: 32GB DDR4 3600mhz VR: Quest 2 under OpenXR (in-game pixel density 1.2, can share full settings if anyone is interested). I'll be upgrading to a 3090ti later this year as well (for more VRAM, DCS eats the 12GB on the 3080ti), which is what's making me look toward a 5900x in general, but I'm very curious if anyone has made a similar upgrade and can share their experiences in DCS. I'm also slapping in some more RAM as well to bring the system up to 64GB, same model and speed as what's in there now.