Forum Discussion

FullDarkMoon's avatar
FullDarkMoon
Member
8 months ago

Future of in-headset creator / editor / tools

Hello all, new Quest user here.  I would have thought this would have been asked already, but my searches have come up empty; feel free to link me to a previous question if it has already been asked.

From the warning in the headset about the built-in creator and the fact that the documentation is all very desktop editor centric, am I inferring correctly that the built-in creator is going to be phased out and Worlds development is going to be Windows-only going forward?  As a Linux user, I've been trying to get the in-headset build tools to work, but I've hit problem after problem (inconsistent scaling, some objects appearing to be locked and unable to be grabbed despite properties showing unlocked, scripts disappearing or not being able to be edited, etc) and am concerned that this will all soon be removed anyway, so am wondering if it's even worth pursuing?

Horizon Newbie

2 Replies

  • T00NAH's avatar
    T00NAH
    Member
    8 months ago

    That is a very touchy topic as of late. From what I've read and personally spoken about with peers is that future support/development for the actual CodeBlocks has stopped. While we are free to utilize them for what they are, CodeBlocks will one day no longer matter, in a way. That is not to say that I don't appreciate popping on my headset during certain build processes. Afterall, I did start with CodeBlocks.

    • FullDarkMoon's avatar
      FullDarkMoon
      Member
      8 months ago

      Cheers for the reply, and sorry for the delayed response; I had hoped for something a bit more official, but it seems Meta's support for its paid products isn't any better than Facebook.

      It's a bit of a shame, as I'm a hobbyist coder and professional sysadmin that has created things in various languages , and I've tried GUI scripting in the past and found actual code easier.  😛  So I'd rather learn how to do this with TypeScript, but without Windows, I can't.

      I even tried installing Windows in a VM, but the Quest tools won't install because it needs a dedicated GPU, and direct GPU access seems to be something only certain hypervisors can do, and VirtualBox isn't one of them.  Might have to try QEMU / KVM and see if I can't get GPU passthrough to work.

Recent Discussions