Messages

Trouble with gamepads is that the sticks are so short that the deflection at the thumb is very small. Risers are cheap and help a bit.

make a 'cameras.cfg' in the helmet folder and add;

ref_rot
{

   x = 90
   y = 90
   z = 0
}
camera0
{
   name = Helmet 1
   position = 0 ,0.095, 0.14  ;LR,UD,FA
   rotation = -20, 0 ; UD, LR             
   fov = 100
}
camera1
{
   name = Helmet 2
   position = 0, 0.095, 0.14
   rotation = -25, 0
   fov = 75
}

I think the classic kicker is just an audio device, the amplifier is like a sub-woofer amp and filters off everything apart from the bass frequencies and then sums the left and right channels together.

If you want to make one on the cheap look for haptic drivers on the web and use an old power amp with the bass up and everything else right down.

https://www.waitingforfriday.com/?p=451

At the bottom of the page is a link to some demo code for VC. I have built a project based on this and it worked perfectly

Its a cheap generic MEGA2560, driver states USB-SERIAL CH340,
 also opened the port to my EDTracker, driver states Arduino Leonardo (was another cheap generic board)

This was just a very quick fudge to see if the ports would open OK..

Code Select Expand

#include <iostream>
#include <windows.h>
using namespace std;

int main()
{
    cout << "Hello world!" << endl;


    // Open serial port
HANDLE hComm;
hComm = CreateFile("\\\\.\\COM9", GENERIC_READ | GENERIC_WRITE, 0, 0, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, 0);

if (hComm == INVALID_HANDLE_VALUE) {
printf_s("\nSerial port failed\n");
cout << "Fail" << endl;
}
else {
printf_s("\nSerial port successful\n");
        cout << "Port open" << endl;
}
DCB dcbSerialParams = { 0 }; // Initializing DCB structure
dcbSerialParams.DCBlength = sizeof(dcbSerialParams);

//Status = GetCommState(hComm, &dcbSerialParams);

dcbSerialParams.BaudRate = CBR_9600; // Setting BaudRate = 9600
dcbSerialParams.ByteSize = 8; // Setting ByteSize = 8
dcbSerialParams.StopBits = ONESTOPBIT; // Setting StopBits = 1
dcbSerialParams.Parity = NOPARITY; // Setting Parity = None

//Status = SetCommState(hComm, &dcbSerialParams);

COMMTIMEOUTS timeouts = { 0 };
timeouts.ReadIntervalTimeout = 50; // in milliseconds
timeouts.ReadTotalTimeoutConstant = 50; // in milliseconds
timeouts.ReadTotalTimeoutMultiplier = 10; // in milliseconds
timeouts.WriteTotalTimeoutConstant = 50; // in milliseconds
timeouts.WriteTotalTimeoutMultiplier = 10; // in milliseconds
CloseHandle(hComm);
    return 0;
}

Cannot be much wrong with your code; installed code::blocks and GNU compiler and it worked fine opening the port to my arduino using;

// Open serial port
HANDLE hComm;
hComm = CreateFile("\\\\.\\COM9", GENERIC_READ | GENERIC_WRITE, 0, 0, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, 0);

I have devices on COM5 and COM9 and it worked for both

If you want to try something other than studio;
http://www.codeblocks.org/downloads/binaries

you want; codeblocks-20.03mingw-setup.exe

go to settings>compiler>

for GNU GCC compiler go to 'toolchain executables' tab and auto detect path to load in the compiler module

Good to go..

Not a studio expert so this is a bit desperate but should you have (for classic c);

#include <windows.h>

and

HANDLE hComm;

at the start of the code?

Serial is pretty dumb, so when you open the port it will only look at the PC (host) end.

Worth trying hyperterminal to check that it can open the port OK and send some data. It will basically run stand-alone from the directory without any install.

If you try it, in the options set it to echo send and receive and you should be able to see all the data

You could try this slighly differnt call https://support.microsoft.com/en-us/help/115831/howto-specify-serial-ports-larger-than-com9

I am wondering, that if you have the ARDUINO environment open at the same time has it already reserved COM3 for its (exclusive) use?

You can download and run the old hperterminal from windows XP to test serial comms on win7 and later
https://www.instructables.com/id/Port-Hyperterminal-to-Windows-7/

This is a good link for understanding USB https://www.waitingforfriday.com/?p=451

It should be possible to send stuff using the ARDUINO virtual COM port. You should see a COM port listed in your system hardware if all the drivers are installed OK. Never tried it though so I am not sure what the limitations would be but I guess the ARDUINO has an FTDI chip attached to the USB connector and just passes the serial data to the chip, you might need to change some jumpers as I guess at the moment its connected to the programming pins of the ARDUINO

A quick read and the base model ARDUINO use an FTDI chip to emulate a classic COM port - they do not have USB unless you get an add on board. So you should just be able to open the port and talk back and forth across the Arduino virtual COM port.

The createfile call looks OK, I would remove all the remarks just in case though
hComm = CreateFile("\\\\.\\COM3",GENERIC_READ|GENERIC_WRITE,0,NULL,OPEN_EXISTING,0,NULL);

 - can you confirm the virtual COM port driver is installed as COM3?

USB and serial port are very different.
If you really want serial then use a USB to serial device converter (FTDI chip) that creates a classic COM port through a driver.
If you want true USB then you want to find a c USB class module that will let you cretae a handle to a HID (the only generic USB class you can create without a licence from MS).

By far the easiest way is a generic network board for ARDUINO (about £5) and use UDP

Please just release a quick VR hotfix before looking into new features like that.

Unfortunately it's not so easy.
So far investigation on the virtual rider changes has been inconclusive, with no difference between the Beta18b and Beta18c behaviour.

Maybe an intermediate ( bugged ) version of the code has been released by mistake? 

After a lot of 18b laps my first impression of 18c was significant understeer, trying to fix it just lead to excessive lean angles and all the problems that creates with any form of camber. Personally, my first thought was tyre profile issues.

Would it be possible to add, or allow an option in config for a 1P camera that is fixed just in front of the rider eye position rather than 'floating' around the proximity of the neck location?

A CarED would go a long way to generally improving the appeal of mods for WRS - I started a sidecar mod (using the invisible 4th wheel) but trying to figure out the GEOM was just a showstopper as its even more complex than GPB to sort out.

I just had a go and it converts suit transparency to black - which is odd because helmet visors work OK as paints