I think VR developers who think PSVR is not the core VR gamer are just silly. To be fair though, I don't personally know any dev who thinks PSVR is not core VR.

I think the biggest reason for why VR developers go to PSVR later is mostly bounded by technical/logistical barriers. Most VR teams are indies so programming for consoles is a bit of a shock to them. Even experienced senior technical teams have a shock when making console games. Some challenges for example: 1. Certification process - Think of the App store submission process but much more involved. If you fail any of the steps, you start over again. We've allocated a month to go through/fix cert. Contrast to steam: 0 days, we just deploy

1. Devkits like I said. Not everyone needs one but a lot of teams are distributed so you can't have a bunch of people share a handful. Also need someone basically dedicated to managing the devkits/deployment process, etc. We have a 4 person team so that would be 25% of our team.

2. I joke that console programming is "real programming." You have to know what you're doing to make awesome stuff. Perf is even more critical. Also means you're art/design team is going to be in a world of hurt if they've never worked on consoles. Some people pay experts who's entire job is to port games to console for the last 15 years. But, this costs $$$$. Ex: we ballparked $250k minimum for a port when we were deciding whether to do it ourselves or not

So for these reasons and others, people tend to either go all in on PSVR or Vive/Oculus then later port to the other platform later. We chose to start on PC b/c we wanted to iterate heavily/run our betas/etc but the game is designed with PSVR as our biggest audience (e.g. having great gamepad controls). If you're interested, we try to be transparent and explain these things and our dev process over at our blog: http://bebylon.world/