Whenever i choose to defer an update to Pimax Play, I lose the opportunity to install the update subsequently. Whether software or firmware, PP tells me that my system is up-to-date (when it clearly is not). This has been going on for a very long time, so why has Pimax not addressed this?
Which version do you currently have installed, and which version are you trying to update to?
Also, please note that new patches are rolled out in batches. As a result, not all users will receive the update notification immediately when they click “Check for Updates.”
1 Like
Why not? Please explain.
1 Like
I’m still on 1.43.9 and every time i check for updates it says it’s up to date. I think the updater is broken or the rollout schedule is just some guy selecting random serials every once in a while
I can’t access my system for a couple of hours, but this is not a new thing - it has never been any different.
Typically, I turn the Super 50 ppd on after I have set up my plane and am ready to taxi. At this point, I don’t want to interrupt MSFS2024, so I try to defer the update.
This happens every time, so it is actually irrelevant which version of PP I am using.
I have just checked and can advise that I am currently on version 1.43.3.9 of Pimax Play.
This problem is nothing new. It also used to occur when I was using the Crystal Light. It is not peculiar to any particular update - it happens every time I try to defer an update.
I cannot understand why Pimax has not addressed this,
I have no desire to completely reinstall PP. Update should just work!
I do not believe it is equipment-related, as this problem has existed over various systems (both Intel and AMD). I am using a 5090, with 64gb of RAM.
Yeah I’m on 1.43.9 and it tells me I’m on the latest version. Can’t say I trust the system much tbh. As Braul says, either bugged, or it’s some manual job.
1 Like
Also I just noticed that all my PiPlay settings randomly reset today (eg it started automatically and minimised to window on closing it, rather than offering to shut down).
Usually all I do is launch, do some VR, close again. So no idea why it lost the settings today.
1 Like
The update will be rolled out in batches, with the rollout expected to be completed within two weeks.
Which version?
1.43.9. Hopefully just a random one-off occurrence, never happened before.
Pimax’s poor slow roll out seems to be the same ssu. Please e they seem to b doing a terrible idea 
of not having standalone download going through the updater.
Makes reinstalling wh n needed a much bigger pain.
Did you try the 1.44.2 instead?
I haven’t yet because I’m nervous about it, even though current performance is a bit low.
Will also update to the latest DA firmware. Can you tell me if there are currently any known issues or user reports for the DA LH running 1.44.2 and latest fw?
We haven’t received any reports of significant issues with that firmware when used with the 1.44.2 release.
However, several users have reported that tracking performance appears to have degraded after updating to the recent beta 2.0.1 build.
1 Like
OK good to know thanks, I’ll try it. And do you recommend an Nvidia driver version (or should I avoid latest version)?
On that note, I still have very random behaviour with 3DOF vs 6DOF. It seems less frequent with a well lit room, but it still happens.
Usually I can fix it by closing my game, restarting the service via PiPlay, reconnecting the headset to the lighthouse, and trying again.
Perhaps the connection is easily broken, and although PiPlay still shows the device as connected, this has caused 6DOF to be lost.
Updated to 1.44.1 and 1.0.3 fw, seems fine 
Was going to ask how I get 1.44.2, didn’t see a link and can’t get Pi Play to detect a newer version, but I found a link via Reddit 
Is that the only place that links to it?
https://dlappstore.pimax.com/release/play/PimaxPlaySetup_Release_ToC_V1.44.2.283_202605201138.exe
1 Like
So far, is everything working well with the 1.44.2 build?
Have you noticed any abnormal tracking behavior or other issues since updating?
Still on 1.44.1 at the moment. I’ll update to 1.44.2 and update if any problems - it’s just an additional hotfix right? Shouldn’t have any impact presumably.
Tracking - I think what is happening is that a brief block of LoS will revert the headset to 3DOF. On PiPlay itself it will not show as Disconnected, this would take a block of a longer period of time. So I was unaware that it had occurred until in-game. And I can fix it by quitting the game, restarting the service in PiPlay, and reconnecting the headset. I think low light is not really the issue. I would say that this level of sensitivity was not present with the 5k+ and 8KX, but it can be managed fine.
I still have the issue with noticeable blur on movement, and others have reported it too. So I look forward to any answers from the devs about whether this can be fixed via profile, firmware, PiPlay update etc