Definition of the path to ./blender in config .xml not taken into account (for dynamic .blend mod at blenderVR start)

[PyrApple]

While the configuration file (.xml) can be used to define the path towards blender binary* it doesn't seem to be taken into account, as e.g. a misspelled declaration throws no errors in BlenderVR run.

Line concerned in .xml configuration file:

[...]

*(blender bpy used to modify the .blend on the go to add blender-vr related features prior to the BlenderVR run)

[dfelinto]

In fact I think blender should be defined in the system, just like blenderplayer is. It probably makes this fix simpler too.

[PyrApple]

Fine by me,

(some may complain that you can't have blenderplayer nor blender pointing towards non blenderVR versions.)

David

Le 19 févr. 2015 à 18:48, Dalai Felinto notifications@github.com a écrit :

In fact I think blender should be defined in the system, just like blenderplayer is. It probably makes this fix simpler too.

— Reply to this email directly or view it on GitHub.

[dfelinto]

By system I meant:

<computers>
  <system>
    <blender executable="MYSPECIALPATH/blender">
    <blenderplayer executable="MYSPECIALPATH/blenderplayer">
  </system>
(...)
</computers>

[PyrApple]

++ (no ambiguities that way)

Le 19 févr. 2015 à 23:01, Dalai Felinto notifications@github.com a écrit :

By system I meant:

(...)

— Reply to this email directly or view it on GitHub.

[dfelinto]

For the records, I believe the reasoning behind this is that the loader is called only once, while the player is set for each of the clients.

[dfelinto]

Issue fixed (712bf70b) without changing the XML definitions