it wasn't very clear but of course you can name the textures as you like :) just said test.png and test_nmap.png because that's what I used in the venus record :) to add a normal map just add normal_map = filename.png...
best, eleni On 19 September 2011 20:20, Eleni-Maria Stea <[email protected]> wrote: > Hello Fabien and everybody else :) > > I managed to finish the bump mapping for the ESA SOCIS (of course > there are still many minor things to do in the code such as improve > the coding style, add doxygen documentation parameter etc... but I > thing the heavy stuff is over now). > > The code is here: https://code.launchpad.net/~hikiko/stellarium/socisplanet > > and here are some screenshots using a random texture and its normal map: > (I experimented in Venus) > > http://i.imgur.com/GgW0F.jpg > http://i.imgur.com/Wedo9.jpg > > Here is the same rendering without the texture (so that you can see the > bumps): > > http://i.imgur.com/urvzj.jpg > http://i.imgur.com/4xNPe.jpg > > If you want to run it here are the maps: > > texture map used: http://i.imgur.com/6mBWn.jpg (you need to convert it > to png and name it "test.png") > normal map used: http://i.imgur.com/TGcsF.jpg (you need to convert it > to png and name it "test_nmap.png") > > then you can replace the record for Venus in ssystem.ini with the > following and copy the maps inside the texture folder: > > [venus] > name = Venus > parent = Sun > radius = 6051.8 > halo = true > color = 1.0,1.0,0.9 > tex_map = test.png > normal_map = test_nmap.png > tex_halo = star16x16.png > coord_func = venus_special > lighting = true > albedo = 0.77 > rot_periode = -5832.479839 > rot_rotation_offset = 137.45 > rot_pole_ra = 272.76 > rot_pole_de = 67.16 > #rot_obliquity = 178.78 > #rot_equator_ascending_node = 300.22 > orbit_visualization_period = 224.70 > atmosphere = 1 > > Then it will probably run :) > > I think that next task should be: > find height or normal maps from nasa, esa etc > if this is not possible maybe I should add some code that generates > random maps (using noise for example) > and then of course write the doxyzen documentation. > > What do you think about this? > Do you think that I should do something else before this task? (for > example try to implement something else from the blueprints?) > > Thanks in advance :)) > Best regards, > Eleni > ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA Learn about the latest advances in developing for the BlackBerry® mobile platform with sessions, labs & more. See new tools and technologies. Register for BlackBerry® DevCon today! http://p.sf.net/sfu/rim-devcon-copy1 _______________________________________________ Stellarium-pubdevel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel
