Q2 is between July and September?
It’s so late …
Does this mean that it is a general consumer release?
The delivery date display of the kick starter is still in February.
1 Like
I had hoped you would address the ces issues @deletedpimaxrep1
5 Likes
Q1 is Jan-March, Q2 is Apr-June, Q3 is July-Sept, and Q4 Oct-Dec. @deletedpimaxrep1 Thanks for the update.
3 Likes
Its April <-> June dude…
thank you everyone!
Well, still a little more, thank you for 4K!
We hope to improve a number of problems and make it a wonderful product.
I support you, PIMAX TEAM!
3 Likes
Werent we told there woukd be a detailed list of the issues that were encountered at ces? This post makes it seem like there were no issues with v5 but that apparently isnt the case at all.
5 Likes
Any update is welcomed but I was expecting a much more detailed update in regards to the pending issues. Where is the status update for the 90Hz issue? Are you changing the display bridge? What’s the status with CES issues? Controllers & base stations?
5 Likes
Xunshu, thanks for the details on the evolution of the prototype, and it’s good to see that you believe in being near to the M1 version irrespective of the issues V5 had at CES.
However, as some have already mentioned here, we were told by Pimax to be provided with, and are expecting, an update which addresses the issues the V5 apparently had - in your statement there is hardly any mention of them, and given that some of the issues like the convergence/IPD/distortion issue(s) perceived by a number of reviewers have been around essentially since day 1, and have been a flaw, a negative point to note, in many of the reviews over the past 6 months, I believe some of us worry if your silence on them and your statement to be moving on to the M1 without a V6 inbetween means that these issues will not be resolved in the production unit.
You can see the list of issues in this thread:
http://community.openmr.ai/t/summary-of-known-issues-with-pimax-8k-5k-hmd-v5-that-needs-fixing/5073
The 90 Hz issue probably is still subject to the March update after having tested alternative hardware?
I do not want to be negative but I think this status update will leave some of us concerned and a bit disappointed - the expectation was simply that Pimax address what caused the flaws and if they know how to resolve them.
6 Likes
Thanks, the team is fine-tuning v5, we will update the progress in the forum within the next two weeks.
6 Likes
Meaning that Pimax will address each of the issues and whether these can be resolved or will remain, when you update us in two weeks ?
1 Like
@deletedpimaxrep1 Has the pimax team considered getting in touch with futremark? VRMark - The Virtual Reality Benchmark
They have a special lab that accurately measures the “motion to photon” latency and can provide detailed numbers of aspects of a hmds performance. It might be really helpful to run the M1 with these guys to get a sense of a non subject analysis of its performance.
6 Likes
@deletedpimaxrep1 Does the brainwarp technology already works?
2 Likes
Thank you PIMAX for shouldering the additional development costs that come with extended time window and holding out a while longer to please your consumers. Good luck to you all over the coming months.
3 Likes
@deletedpimaxrep1 thank you very much for the update.
A lot have already posted what the next updates should ideally entail, please do address each issue that has been discussed regarding v5 at CES specifically and state how you intend to overcome that obstacle. If you feel that this might be in breach of understandable trade secret considerations, just say so and we’ll understand.
I would also like to emphasize the importance of the select focus group entailing community members which you already referred to. This will not only give you brutally honest feedback on a B2C base but it will help tremendously in your backer communication.
Now I don’t know if you have already decided on which individuals to include but going by their input on these formus, I would personally like to nominate @Heliosurge, @Cdaked, @SweViver and @Sjef. All of those appear to be knowledegable, have a relevant following and can write statements that are objective and non-incisive.
8 Likes
Has the closed group from the community for testing M1 been chosen yet? If not how do we apply?
2 Likes
Try contacting @deletedpimaxrep1 through PM
2 Likes
Sorry but why didn’t you say that directly at the end of your progress update ? No intention to be rude, but by not doing so you sound like you were trying to skip this promise but finally had to change your mind because you see some people not fully happy with the content of your progress update… It is not surprising some people are lacking confidence in pimax when you behave like this.
That being said, I personally would be reassured if I could know who will be your beta testers. I hope they will not be chosen solely based on popularity (no offense to anyone) but on exigency. I would be reassured if the beta testers were very unforgiving people like Ben Lang from roadtoVR who spotted the CES v5 issues with great accuracy. Will this guy be proposed to participate in your M1 beta testing ? And Norman and Jeremy from Tested ?
I would be much more reassured by knowing such hard to please people are involed in your beta testing than by any feedback from a new roadshow with the M1.
Yes the latter may have some interest in collecting a wider diversity of feedbacks but you should already have collected many of such informations from your previous roadshows. I think focusing on beta testing with a few hard-to-please VR people would be much more efficient into helping you refining the headset, while a new roadshow sounds more like advertising than beta testing.
I’m not sure spliting your ressources between a new roadshow in the meantime you are beta testing is the best idea. The priority is to make the product right and then the quality of the product will speak by itself and help further advertising and sales. It doesn’t sound the right time for more advertising from another roadshow before the product is ready for production New positive feedbacks from a M1 roadshow would become unsignificant if the backers were receiving a headset with remaining flaws or below the expected VR quality standards. Just look at how the flaws reported from CES v5 were able to harm the confidence from many people despite the very good feedback just 2 monthes ago from previous prototypes. You should learn from this and focus on a proper beta testing, not advertising.
I don’t want to hide it, at the present time I’m not that reassured because of what I see from your behaviour. Being confident about solving current issues and giving the impression you tried to skip the promised discussion about those issues leaves me the feeling you could easily understimate the VR quality we (at least I, but I’m certain I’m not alone) expect from your product. I would be reassured if you were showing taking measures to create a handrail preventing you from being tempted to minimize some flaws, consciously or not because you may think in all honesty that a given flaw will not be important to the users when in fact it could be. Hard-to-please beta testers would minimize that risk a lot, it would be that handrail which I’m not sure feedbacks from a roadshow would be (at least not to the same extent).
I know I may sound nitpicking, or over suspicious, or condescending (who am I to give you advices as you know your job) but sorry, if Ben from roadtoVR (and a few others) haven’t raised the convergence issue (3D overlapping) from the v5 at CES, or mura, would have we heard about it from you, pimax ? And if not then what other underestimated flaw(s) could be discovered when the final product will arrive in thousands end-users’ hands ? Because of how CES went and how you dealt with us about those reported flaws I still have that fear unheard flaws will only emerge when the product will arrive in my (our) hands.
12 Likes
Waiting with baited breath for the response to the v5 CES critics and the above response tells me everything is fine and things just need fine tuning. O.o. They have 7 weeks remaining.
Given they will be mass producing the M1 in Mid March (just 7 weeks from now) I would say, if they can fix all the visual issues with “fine tuning” then I will be astonished at their engineering skill. 7 weeks is nothing when mass producing something, in fact you could easily spend 8 weeks making sure everything is ready before it goes on the line. Never mind changing anything in that time.
I am not sure if I should be excited or worried at this minuscule time frame for all the as yet unresolved issues. I will er on the side of caution due to lack of any meaningful responses to questions repeatedly asked. Constantly saying you will update in the forums and then posting a historic time frame instead with a 4 point bullet list of how you will fix v5 leaves me with a vote of no confidence.
Yes, I would love to eat my hat.
7 Likes
Thanks for the update!
Some grumpy points to consider:
- Read the update thoroughly instead of posting questions that were answered in the original post. Can’t believe I have to point that out.
- There is a Swedish saying that translates “Much wants more.” meaning when someone gets something they’re never satisfied and only keeps asking for more. This is what we got for now so try to come to peace with it.
- Hey, Captain Obvious!..
- I need more coffee.
5 Likes
Thanks for the update Xunshu Li¡
If you can please give us an update on basestations and controllers
1 Like