Page 6 of 6
Re: Planetary code
Posted: Sat Apr 12, 2014 9:18 pm
by Deus Siddis
ezee wrote:Thank you for this tip .
But i have already tried that ( at my first attempt
) , with the llama , without success.
Okay I just successfully converting the llama to obj on windows 7. (What operating system are you using by the way?)
I had to run windows
Command Prompt as administrator to get mesher to work through it.
Then, in command prompt, I navigated to the main vega strike directory where mesher needs to be located to work correctly and where I had moved the bfxm to.
And then I used the command:
Re: Planetary code
Posted: Sat Apr 12, 2014 10:04 pm
by ezee
Thank you for the help .
I have windows xp .
I made a shortcut of the command prompt in the folder of Mesher .
Then paste the .bxfm in the same folder
With the same parameters than you in commandline , mesher crashes ( .mtl file and obj
are created but with 0 ko .)
It's the 0.5.1 rc1 release
Re: Planetary code
Posted: Sat Apr 12, 2014 10:04 pm
by ezee
sorry , double post ...
Re: Planetary code
Posted: Sun Apr 13, 2014 12:05 am
by Deus Siddis
Well that is strange, I have done the same conversion on xp many times (and using the same release of VS too)...
Which folder is mesher sitting in?
Re: Planetary code
Posted: Sun Apr 13, 2014 11:39 am
by ezee
The path is something like :
d:/program/experimental/data/...
...where win32 binaries are , with mesher .
I also tried to use Mesher inside the original SVN/bin folder , with same results .
My xp version is service pack 3 , but i don't think that is the problem here .
You suggested to check the admin rights , that could have been a problem under vista
or seven , 8 .
Mesher is able to read the files ( if i do llama.obj llama.bxfm , the output report a bad end of file , where the program was waiting a B) , but it can't write , i will try to find out why . ( read/write access in the folder ?)
Perhaps it's only my local problem , but perhaps other artists that are more shy than me don't report the problems , and go away .
So have a pack of .obj ready to use could be a good idea .
Also in term of productivity ( one time for all conversion )
Thank you again for your help .
Re: Planetary code
Posted: Sun Apr 13, 2014 8:09 pm
by ezee
Back to planets , my road is now :
Libnoise
A portable, open-source, coherent noise-generating library for C++
Tutorial 8: Creating spherical planetary terrain
In this tutorial, you'll generate a terrain height map that can be seamlessly wrapped around a sphere. These kinds of height maps are ideal for creating your own planets.
This height map system could be used also to define raw material zones , for mining purpose .
With flat lands generated for city's etc ...
That's the way i go now .
Edith : I've found a python lib too :
https://sourceforge.net/projects/noisel ... rce=navbar
noiselib is a Python library inspired by the C++ libnoise. noiselib strives to provide a 'Pythonic' interface, without sacrificing speed. The noise generators are implemented using the C Python API.
Re: Planetary code
Posted: Mon Apr 14, 2014 8:19 pm
by ezee
I have played with the Perlin noise generator in c++ , it is cool for setup a planet out of the game . ( the original libnoise create a file on disc , we want to create a file as stream for the gpu )
So we need dynamic generation , and modify the octaves and frequency ( params for LOD ) in game . The only solution i saw was to use the gpu via the shaders , and that's the way peopo' use :
Example of modified perlin noise code:
http://www.sci.utah.edu/~leenak/IndStud ... 20GPU.html
Some cg code are provided as you seen, and Ogre3d supports cG too :
http://www.ogre3d.org/tikiwiki/tiki-ind ... +Materials
I think it could be possible too to implement a procedural code to VS , by following step by step
stages . One step is to find what kind of shaders we could use for the perlin noise factory .
Pyglet could be used to test this planetary code outside of VS first ( but using the gfx format ? ), as it supports shaders , and python can run noiselib too .
Re: Planetary code
Posted: Tue Apr 15, 2014 3:50 pm
by TBeholder
Deus Siddis wrote:I had to run windows Command Prompt as administrator to get mesher to work through it.
What permissions it wanted? Did you try it under Process Explorer?
Re: Planetary code
Posted: Tue Apr 15, 2014 10:36 pm
by Deus Siddis
It does not say anything about permissions, it just quietly fails unless you know to run as administrator. Running VS itself is the exact same deal. Microsoft no longer wants its sheeplebase wandering outside the pen, so it closes the gate to unapproved software anyway it can.
I did not try using Process Explorer (never heard of it until now), what would that reveal?
Re: Planetary code
Posted: Wed Apr 16, 2014 4:46 am
by TBeholder
Gives a log of certain system requests (file i/o, registry access, DLLs), whether they failed, were denied or passed, etc, with filter (e.g. dropping everything not for "mesher.exe"). So if it doesn't have privileges, you see which. Administraton of NT and derivatives to accomodate non-trivial new software without this is mostly guesswork.
Re: Planetary code
Posted: Wed Apr 16, 2014 7:36 am
by loki1950
I never had a issue with it back when I still used XP
and no problem with Win7 now if I can it built on my fedora 20 side
Will post the relevant log snippet to the proper place once I am back *nix side
Enjoy the Choice
Re: Planetary code
Posted: Tue Aug 12, 2014 3:02 pm
by klauss
Deus Siddis wrote:ezee wrote:
So you say that make a .obj is easy ...
Ok.
Do you use Mesher in place and give the paths to the bxfm files ?
Or copy mesher in the folder containing the bxfm ?
Because the paths could be long ya know .
You cannot move mesher because it has dependencies, if I recall correctly.
But you can and should copy the bfxm and move it to mesher. Much faster than typing and mistyping long paths into a command line program.
Ehm... just add mesher's dir to the PATH environment?
Re: Planetary code
Posted: Mon Aug 25, 2014 8:23 pm
by Deus Siddis
Oh yeah...