Hm... it's correct to start spacenavd with sudo so it can open a socket and wait for client connections. That first error message is from libspnav (linked into blender). I took the easy route and installed the spacenavd package in Ubuntu, which also took care of launching it properly. If anyone reading this has daemon-wrangling experience, please chime in and set us straight!
Mike Erwin musician, naturalist, pixel pusher, hacker extraordinaire On Thu, Jul 28, 2011 at 6:22 PM, Stephen M. McQuay <step...@mcquay.me> wrote: > On Fri, Jul 22, 2011 at 10:32:08PM -0500, Mike Erwin wrote: >> Either check out the merwin-spacenav branch now... or wait a very >> short time for 2.59 > > Okay, built the merwin-spacenav branch, and started up spacenavd (As > sudo; it complained about /dev/input/event5 being unreadable as my user) > and then kicked up blender. Got the following output: > > % /opt/blender-spnav/install/linux2/blender > connect failed: No such file or directory > ndof: spacenavd not found > ndof: registering menu operator > Info: Config directory with "startup.blend" file not found. > found bundled python: /opt/blender-spnav/install/linux2/2.58/python > > Thoughts? > > > -- > Stephen M. McQuay > http://mcquay.me/vcf > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers