I have gone back to using the stock Logitech drivers vs using Spaz.Next
They just work. And work well.
All my issues were caused by using this Spaz.Next thing.
My Logitech Radio panels are also working properly now. No more missing display elements.
Spaz.Next has to be the most useless, complicated piece of rubbish I’ve ever encountered.
Which tells me you have absolutely no clue on how to use Spad.
It happens to be one of the best pieces of software around.
SPAD just does not work with MSFS. The reason? MSFS does not provide “aircraft states” feedback to SPAD. It is on the wish list but not implemented. There is the same few people promoting the SPAD software. After buying the Spad software a disclaimer pops up during the install process saying it won’t work with MSFS because MSFS does not provide “aircraft states” feedback but they hope it will soon.
All feedback MSFS can provide to the outside world comes by means of Simvars and they are already supported by Spad.Next. You can read and write them. The problem is not Spad.Next but that MSFS does not provide anything else and some of the those variables are wrongly implemented in the airplanes so trying to read or write them does not produce any effect to whoever tries to use them, no matter if it´s Spad.Next or any other software or script run by a third party addon.
I find this software complex but also very flexible. It´s true it´s for advanced users but I could make Vrisim Boeing Combo panel to work and customize the diplaying of its screens, which is a very old serial panel which such costomization not being even supported by original vendor drivers, so yes it works very well I would say.
Cheers
nonsense. I just used Spad next the other day to map a bunch of PMDG 737 controls to my VKB joystick and i plan to remap some of them to the new STECS throttle they have and i just ordered. That’s going to be an even bigger pain to do because PMDG decided to reinvent the wheel instead of using available simconnect lvars, although now i know a little bit more about what i’m doing in spad.next. I plan to go back and map buttons (and detent settings 
) for additional airframes as well and spad.next will give me 100% more flexibility than trying to map things in the game directly (especially with PMDG planes). I was also able to set up my logitech radio panel using spad to control parts of the MCP panel in the 737 as well.
In my mind, an aircraft state is a setting in which the aircraft is ready to go at a given phase i.e cold and dark, ready to taxi, ready to take off etc. Not sure why i’d need spad.next to control this; it would defeat the purpose to buying button boxes and radio panels if all i had to do is push a button for a given aircraft state. Maybe you can elaborate a little about what it is you’re trying to do with the app specifically with aircraft states
Like Geloxo said, it’s for advanced users and simpit builders. it took me quite some time to learn (and chatgpt helped a little too). But it 100% works for MSFS. Seems a little silly they’d keep selling it if it didn’t work (let alone have a version exclusively marketed for MSFS). Were that the case, it would be a scam by any other name.
You probably know now, but they offer a two week trial for spad.next for the very purpose of finding out if the app will fit your needs (or even work at all for you).
The Logitech drivers are plug & play for me. They just work.
I really tried with Spad but its horribly complicated to use.
It’s nice to have my radio panels working properly again.
That’s my experience.
@geloxo. I am a 79 year old and have both the Vrisim Boeing and Airbus Combos. I have had little success trying to implement them in spad.next. Would you be willing to share your “snippets” for the Boeing unit? I would be most grateful if I could use it within MSFS. Thanks.
I only use Spad because my Class Echo requires it. I do use it for my Logitech radio and multi panel because it fixed issues I had with the knob increments. I use the default profiles spad has for the Logitech panels, and I use snippets provided by the developer of the Class Echo for said Class Echo. I’ve never bothered to learn how to program anything myself with Spad. It works great for what I need.
I don’t think that is correct to say that Spad is useless.
I don’t have Spad and for my personnel use, fortunately the Logitech drivers work OK in MSFS (also have worked in P3Dv3 and v5-with FSX diver!, X-plane 11 and 12, and Aerofly 4-FIP excluded-).
I had some problems with the FIP but with a powered USB all is OK.
Been using SPAD.NEXT since I purchased FS2020 and no problems ONCE you understand what is does and how to program/set it up. It is not useless…although it does take some time to learn how to use it as it is not “plug and play”. There are lots of tutorials on YouTube if you need help.
Your statement yet again proves what a great place the internet is for disinformation. SPAD has never not worked with MSFS. I fly with it every single day. It also happens to be well supported and continually updated.
So, since you could not figure out how to use SPAD you call it “rubbish”. Once one learns how to use this tool and how powerful it is, there is no going back plain and simple. I am sure those that use AAO, Mobiflight, and FSUIPC feel the same way. However, all of these tools require a time investment from the user to learn how to utilize them.
What nonsense.
Spad.neXt - worth every penny.
I can’t imagine flying FBW,PMDG,GA … without Spad.next.
I use both Spad and the Logitech driver enabled Radio and Switch Panel in conjunction. Works great !
Quick! Someone tell Les O’Reilly that spad doesn’t work!
/Spad works with fs20, it works well, and it’s design is rather intuitive.
I’m sure if you are a software engineer or your brain is wired that way, Spad is fantastic.
I have struggled with it and it messes with my setup.
I run the Logitech drivers and everything just works.
I want to be flying, not wading through some complicated, dogs breakfast.
Keep it simple.
How did you get that to work ?
No, I don’t. I’ve tried though. Way beyond me.
Youtube search for Les O’Reilly, and take you’re time to watch his video’s. I use Spad.next since FSX
Sure Warmage1944, no problem. First of all let´s double check the config process to let the unit and Spad connect. Do this just once, before starting game. This works for any of the VRInsight panels:
You need to install the FTDI serial drivers. VRInsight original installer also included them but latest ones are available here: VCP Drivers - FTDI
Run Spad and add new device selecting:
Devices → Serial devices → Add new device → Set COM port and protocol
Set VRInsight as protocol and select the COM port that is used by the FTDI serial drivers. You can see which one it is going to Windows device manager and checking the “COM and LPT” section at the bottom of the list.
You need to copy it to My Documents, where you will find a “\SPAD.neXt\profiles” folder. Put it in that profiles folder. Then load the profile in the application directly.
IMPORTANT: rename it to “MCP Global.xml”. I had to change it to txt file as forum did not allow to upload a xml file. You can also change the file name to whatever you prefer. Rotaries are functional as well as anything I found which was working via Simvars.
Feel free to play around with it and edit whatever. It shows things like autopilot data, parking brake and tail wheel lock on left screen and the VOR1/VOR2 radials and distances at the right screen.
Cheers
Yes, done all that. I have also tried using the ‘snippets’ thinking they would setup my radio panels.
All I get is garbled or incorrect digits. I pick snippets with a 5 star rating thinking they will do the job.
The FIP’s work ok.
I even bought Spad.Next with X Plane support. That doesn’t work either. I see the Spad.Next option in the X plane 12 plugin drop down, make sure it’s checked but no show. I used Spad wizard to set it all up.
I really have tried. You can only bash your head against a brick wall for so long.
