About Next Level racing motion V3 for simming

So I just discovered something very interesting. I put myself back in my driving position i.e. feet out pressing on the pedals pushing back in the seat and it was absolutely fine!

It seems the actuators need to pull against something (rather than be pushed down by my weight) to work properly and i can replicate this 100%. If it sit ‘normaly’ i get jerky downward motion. If i push backward in the seat it’s perfectly smooth. I tried moving the seat position in case it was a weight distribution thing but that didn’t help.

I’ll await a response from NLR before doing anything but i might consider fitting a couple of rear springs or counterweight.

@ClayishCoast9 Did you just update Platform Manager by any chance? The latest release has a bug that causes a CTD at startup. It’s fixed in the latest beta but until that’s released you might need to roll back.

Yes I did. That sucks. I’m reinstalling MSFS today … NLR app causing the problem didn’t even cross my mind. Thanks for the info.

1 Like

Thanks for the info! I had CTDs as well since the latest update, requested the Beta version to the NLR support, in the meantime opening the Platform Manager after FS is running may mitigate the issue.

Very interesting indeed, apparently my rig is balanced in a way that doesn’t affect the smoothness of the motors.
Thanks for reporting!

@ClayishCoast9 @TELLURICO1975 The CTD is related to Windows Store complaining about the Motion Compensation AppWatcher service. It doesn’t happen on the Steam version. If you don’t use VR Headway Motion Compensation then another temporary workaround is adding FS2020 to the blacklist.

1 Like

Great, thanks! :smiling_face_with_three_hearts:

Thanks for posting this…I too have had random and odd CTDs in MSFS where it immediately crashes when trying to launch and I can’t figure it out despite several attempts to “repair” MSFS and logging out/back into the MS Store and XBox apps… but I did also just update MSFS to the latest beta and also the NLR v3 software too and it never occurred to me that perhaps the NLR software was potentially causing it…I don’t use the motion compensation feature so there was no reason to even consider that but I will add MSFS to the blacklist/exclusion for the motion compensation part of NLR to make sure it doesn’t interact with MSFS (store, or otherwise). I am on the Store version of MSFS.

2 Likes

Argh, why I read this only now! I had spent all my free time the last weekend to get back my MSFS running… No chance! I never thought for the Platform Manager which I updated before the chaos began. I thought it was an Win11 probleme, so I went back to Win10… Now, under Win10 ist works also with the current Platform Manager version…But back to topic:

Excellent work again @TELLURICO1975 and thank you al lot for your really quick profile updates!

@DazzyB2X: I had similar problems in the past, it was just a loose screw that hold my seat at the motion platform.

2 Likes

I seem to be the lucky one as I have not had one problem. He wines a bit about the loss of headset tracking but it really doesn’t affect anything.

Thanks @DazzyB2X That absolutely did the trick! The rolled-back platform manager took exception to the profiles so updated to the latest again. Disabling HeadWay works great.

So now it’s back to trying to land the DC3 without sliding sideways up the runway again :rofl:

2 Likes

After waiting a week, the only response I managed from NLR is ‘we’re looking into it and will get back to you’ so I decided to undertake a few experiments. The results are interesting, and at least for my use case fairly conclusive. This info will be particularly relevant for those like myself who are running the NLR Motion V3 with a GT Track cockpit, but could also be helpful for others depending on your setup so it’s worth documenting.

Id like to start by saying this was all just an experiment for my own curiosity and as soon as I have an official response and recommendations from NLR I’ll change my setup according to their guidance.

TLDR: The Gt Track Cockpit has balancing issues on the V3 when used in it’s recommended configuration.

Long Version: In an effort to troubleshoot my low speed stuttering, I decided to check the balancing by removing the front connecting rods and dampening springs. I also removed my shifter and handbrake (which are connected to the seat frame) so it was basically just me on the seat balancing on the V3’s central pivot.

My seat was about mid way on the sliders and it looked central but the seat instantly fell forward by a huge amount. I had to slide the seat all the way back until it hit the stops before it was even close to balanced. This however presented two huge problems. Firstly unless you have arms and legs like Mr Fantastic, the GT Track doesn’t have enough adjustment to bring the pedals and wheel close enough and secondly the GT Track has a design flaw that means if you slide the seat more than about halfway back the slider adjustment handle fouls on the supporting frame underneath the seat and doesn’t lock in position so the seat moves while you are driving/flying.

The first problem can be solved by moving the V3 forward to the next set of mounting holes in the cockpit frame (you have to leave out the middle set of bolts but they are not necessary anyway)

The second problem can be solved by first removing the seat from the frame. Then removing the slider mechanism from the seat and rotating it 180 degrees so the handle is at the back.

On reassembly, this configuration restricts access to the rear slider bolts so make sure to screw the slider to the frame on the rig first then bolt the seat to the slider. It’s all a bit fiddly but can be done easily enough with a bit of patience. To my surprise the slider is perfectly usable in this configuration and works well actually.

At this point my body is now back in it’s original position but the seat is much further back relative to the V3 pivot point.

I reconnected the front arms BUT NOT THE DAMPING SPRINGS and gave it a try. Voila, beautifully smooth motion in every direction! Unfortunately, the problem with not having the springs connected is that you get some lash in the system when it’s not moving (and I’m guessing the reason it has them in the first place)

So I reconnected the springs and unsurprisingly the jerky downward motion returned as this pulls down massively on the front unbalancing the unit again. At this point I have almost no more adjustment left on the rig so decided to try a counter balancing solution.

The result I came up with was to mount a set of 5.5" trampoline springs to the rear of the unit. I did this by using bolts in the exiting threaded holes on the seat frame and then inverting the rear brace on the GT Track and bolting some eyes through the pre-existing holes.

The result works really well and I now have smooth motion in all directions at any velocity. The side effect is that now the unit is re-balanced, a little bit of lash has returned but it’s only when the V3 is stationary or powered off and it’s worth the trade off IMO.

I’m still weighing up the pros and cons of running four springs vs no springs. having four seems to give a little more tolerance in terms of balancing but puts a little more load on the motors - but it’s a balanced load and the V3’s motors are easily up to it.

One other interesting point is that when I reconnected my shifter and handbrake (quite heavy lumps probably 10KG with the brackets and hardware) to the side of the chair (NLR’s recommended mounting) the stuttering returned so I now have them mounted to the frame of the rig which means they don’t move but i got used to that real quick and is a non issue for me. My HOTAS is fine and not heavy enough to cause issues.

So my takeaway from all this is that the V3 seems just as sensitive to balancing as any other motion rig and is effectively supplied ‘unbalanced’ due to the dampening springs at the front. Whether this poses an issue will depend on how it’s mounted and each use case. For all i know the motors are calibrated to compensate - but it certainly isn’t the case on my unit. Those using it exclusively for driving will likely never notice as the motion is typically fast enough to hide the problem anyway.

I’m highly surprised that NLR don’t mention balancing in the instructions and i wonder how many people use using unbalanced setups without knowing.

Here’s a pic of my don’t try this at home experimental solution for those who are interested:

As an important follow up to my previous post, I finally heard back from NLR Support (almost 2 weeks!)

Apparently jerky movement is a known issue that can arise due to the characteristics of the front springs combined with a low weight. It’s essentially a balancing issue which confirms my experiments.

Their recommended solution is to move the V3 forward and the seat back (which I already did) and remove the front springs.

As the operation of my four spring solution is very close to running no springs. I’ll be taking their advice and making the appropriate changes. I’ll report back after some extended testing.

2 Likes

Hello Everyone,

I have just purchased a NLR v3 platform and use it solely for MSFS2020.

I was hoping to use the profiles created by @TELLURICO1975.

I’m not sure what I’m doing wrong, but each of the profiles seem to reset all the options to a default of 1.00.

I only use the general aviation profile. Would it be possible to update these. Or perhaps share a screen grab of the settings to make the NLR V3 platform as realistic as possible.

Thank you in advance. :slight_smile:

I am using platform manager version 2.125.1.0 and the most recent version of MSFS2020 (run from DVD, not via steam).

Once again, thank you.

The Lurker :slight_smile:

That’s normal, my profiles are made altering the C++ code generating them, You can use those sliders to fine tune my profiles to your liking, but if you leave everything to 1.00 it should work already simulating the Gs.

Let me know if it works!

Hello There,

Ah, I understand now. Thank you.

I’ve tried the profile on my Piper Seneca. It works perfectly thank you so much.

Can I “buy you a coffee” perhaps?

Thank you for taking time of develop and share this valuable resource.

Kind regards

Lurker

Great news!
I will DM you for the donation :slight_smile:

Hello, reading your post was very interesting I found a V3 at a discounted price and decided to
purchase one, I wanted to combine it with the NLR Boeing simrig but I am not sure if it is compatible, any thoughts?

Otheriwise there is the Motion Plus that with an adaptor it’s should be compatible I still have few days to change my order however the Motion plus is 500usd more expensive.

As of today would you still raccomend the V3 over the Motion Plus?

Thanks Jivan

It’s not compatible with the Boeing. I use the GT-Track myself.
The advantage of the Motion Plus is that the whole cockpit moves, it’s (probably) compatible with the Boeing and you can add a second one for a real heave DOF.
I have never used one though.

Hi, thanks for your reply I like the fact that the whole cockpit moves and it is compatible with the Boeing cockpit however all the review I saw were for racing sim so I am not sure if I would feel movements like the V3 version.

Unfortunately I have no experience at all with the Motion Plus, so it’s very difficult to give suggestions. From what I heard it’s less responsive.