Vjoy Failed

[lucidcreation]

Trying to use this for th first time direct from windows exe and data link shows this failure. Any ideas?

[scott-vincent]

The use of vJoy is optional so the message being displayed is harmelss and everything should still function normally. I will update the code so it only complains once if vJoy is not installed.

[scott-vincent]

Message will be suppressed in next release.

[lucidcreation]

Ah ok. I don’t have vjoy so it sure what it is to be honest.

[lucidcreation]

Have tried a flight this evening and the instruments are dead following the above error. You can see it says no data link. This is all on the same machine. I’m wondering if the vjoy error is stopping the instruments continue to function. They’re also still dim. The aircraft was in flight at the time by the way.

[scott-vincent]

I've fixed the error. Please download version 1.7.3 of both Instrument-Data-Link and Instrument-Panel. You should only see the vJoy error once now.

If Instrument-Panel is showing No Data Link then it is failing to connect to Instrument-Data-Link. Check the output in the Instrument-Data-Link window and you should see a message to say that Instrument-Panel has connected. You will get another message when FS2020 connects. Once they are both connected and you spawn a plane at an airport the guages should be working.

[lucidcreation]

After the vjoy fails shown in the first image the instrument-data-link window it just stays like that. It doesn’t show the instruments have connected or show any further output. I’m using a Just Flight PA28 Warrior, not sure if that makes a difference. I was going to edit the default json to just show the basic six pack. Jason BinghamSent from my iPhoneOn 4 Jan 2023, at 06:21, Scott Vincent ***@***.***> wrote: No, the vJoy error shouldn't matter. What output do you get in the instrument-data-link window as the intrument-panel is failing to connect to it. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[lucidcreation]

Will test the new release

[lucidcreation]

Got it working. I changed the IP in the three json configs to my machine rather than localhost / 127. Do the configs cascade in loading or is just default used unless you specify when loading the exe?

[lucidcreation]

This works great now, donated :-)

Is there a way to make the instruments windowed? Or change the window size? I use a portrait monitor for the instruments.

[scott-vincent]

I'm glad you got it working. The donation is very much appreciated. You can make it windowed and change the size but it would mean building the source yourself although it's not as hard as it sounds. You would need to download Visual Studio 2022 Community Edition and also the FS2020 SDK which is available when you switch FS2020 to developer mode.

[scott-vincent]

Actually, you won't need the SDK if you are only building the Instrument Panel but you will need the Allegro graphics library.

[scott-vincent]

Scratch all that. I've created a new version for you so just download the latest version. The following new settings have been added to the settings file:

"Monitor": {
"StartOn": 0,
"Fullscreen": true,
"Width": 1200,
"Height": 800,
"PositionX": 0,
"PositionY": 0
},

So just set Fullscreen to false then set whatever you need for the size and position of the window.
By the way, no the configs don't cascade. The default one is just there for reference in case you totally mess up the instrument-panel.json one.

Enjoy!

[lucidcreation]

Wow, you’re a star! Jason BinghamSent from my iPhoneOn 5 Jan 2023, at 07:51, Scott Vincent ***@***.***> wrote: Scratch all that. I've created a new version for you so just download the latest version. The following new settings have been added to the settings file: "Monitor": { "StartOn": 0, "Fullscreen": true, "Width": 1200, "Height": 800, "PositionX": 0, "PositionY": 0 }, So just set Fullscreen to false then set whatever you need for the size and position of the window. Enjoy! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>