r1per / mousetovjoy Goto Github PK

The function "newFile" in the FileRead class is accessing a position outside of the "checkArray" length, which may result in accessing a protected memory region (Segmentation fault).

The issue is the maximum value of 'i' is 32 but the checkArray in that case is 23:

// Segmentation fault
for(int i = 0; i < 32; i++){
    if (tmp == checkArray[i]) {
        _resultArray[i] = value;
    }
}

I think a simple fix can be like this:

// fileread.h
// { ... }    Others includes
#include<vector>

class FileRead {
public:
    BOOL newFile(std::string fileName, std::string checkArray[], size_t checkArraySize);

    double result(int number) { 
        if (_resultArray && number < _resultLen)
            return _resultArray[number];
        else
        {
            // Some error handling
        }
    };
private:
    size_t _resultLen = 0;
    double* _resultArray = NULL;
};

Each time you call the 'newFile' function, it will free the old memory if it exists and allocates a new one to store the results.

// fileread.cpp
BOOL FileRead::newFile(std::string fileName, std::string checkArray[], size_t checkArraySize) {
    if (this->_resultArray)
        free(_resultArray); // Free de old allocated memory
    this->_resultLen = Lenght;
    if(!(_resultArray = static_cast<double*>(malloc(sizeof(double) * Lenght)))) // Allocate a new memory ( can be done with 'new(double[size])' )
        return FALSE;
    ZeroMemory(_resultArray, Lenght * sizeof(double));
    std::ifstream file(fileName);
    if (!file.is_open()) 
    {
        printf("Config file not found\n");
        return FALSE;
    }
    // { ... }    Code
    for(int i = 0; i < checkArraySize; i++){
        if (tmp == checkArray[i]) {
            _resultArray[i] = value;
        }
    }
    // { ... }   Code
    file.close();
    return TRUE;
}

Exactly the same problem as other guy had in 1.5 release, tried all the same steps and cant run the program.
I wonder if anyone figured the fix for that.

I'm not sure how you implemented it but the wheel is constantly going left, even when stationary.

I'm using the recompiled version x64. Almost buttons works only Handbreake does not detect, same with Mouse axis in Assetto Corsa, rFactor but LFS works fine.

How i can add custom buttons?

It seems kind of confusing to me, I didn't quite understand that
LONG lButtons; // 32 buttons: 0x00000001 means button1 is pressed, 0x80000000 -> button32 is pressed

I tried to follow that
https://github.com/R1PeR/MouseToVJoy/blob/master/MouseToVJoy/vJoy.cpp#L90
But I didn't understand the hexadecimal of "else"

Using 1.6 Beta 2, when turning the option Use Mouse to 0, it still uses mouse buttons.

Edit: I'm an idiot

There's a lot of options in the "secondary" tab including camera controls, how do I change them? There's a separate keyboard column but that doesn't seem to work in game.

Hi, i love your program, actually is much better than any mouse scripts from GlovePie or FreePIE but is very boring because i can't configure the Gearshift. Would be so cool if you could add this options on "config.txt":

GearshiftUpKey
GearshiftDownKey

Hello, did you try play project cars 3? I run this program, set steering wheel as controller in settings, And still steering is too slow like with keyboard,

When i open the MouseToVJoy from 1.5 i got 3 errors of missing dll:

"A code execution can not continue because MSVCP140D.dll was not found. Reinstalling the program to correct the problem."

"A code execution can not continue because VCRUNTIME140D.dll was not found. Reinstalling the program to correct the problem."

"A code execution can not continue because ucrtbased.dll was not found. Reinstalling the program to correct the problem."

So after put them on SysWOW64 for try to fix this i got a other error:

"The application could not be initialized correctly (0xc000007b)."

As you can see in the screenshot below, version 1.4 works correctly:

I recently tried using your program for asseto corsa and it worked perfectly, but the problem is it ignores mouse acceleration/enhanced pointer precision. This makes it impossible for me to drive properly since when I originally learnt mouse steering on LFS ~3 years ago I did so with mouse acceleration active.

I'm not sure if there is anything you can do about this (a way to toggle raw input on/off, or if you can't do that with vjoy maybe you could add your own mouse acceleration setting?), but if you can I'd greatly appreciate it.

just a small spelling mistake.