This thread is for contributors to the libNurbana final integration inside blender (clik here)
This is not a place to give your opinion about NURBS general usefulness (vs polygon modeling),
otherwise check Wizzleteet’s thread if you are interested by the project history or general discussion.
Background:
- generous donator of the Nurbana NURBS core: Justin Shumaker aka Twingy
- project coordinator from the foundation: Campbell Barton aka Ideasman42
- original integrator and mentor: Emmanuel Stone aka Eman: firstnameDOTlastnameATgmailDOTcom
- blog manager: Claas Eicke Kuhnen aka Cekuhnen
Main developer: Laurynas Duburas aka Ladu mentored by Emmanuel Stone
parent links:
Blender for Architecture
Blender Foundation wiki
current state (October 2009):
- Eman has ported the code to the 2.5 base: new subversion branch
- Cekuhnen has committed a UI design proposal
Previous state:
* 03/05/09:Fixes for curve splitting and knot calculation
- 02/19/09:
New split tool
* 01/24/09:
Support added for cyclic surfaces and weights to Degree Elevate
- 12/25/08:
Welcome to Laurynas Duburas, who works in silence with Emmanuel Stone on various issues/improvements:
* 10/04/08:
- completion of the feature request
- active svn branch (compiling with scons)
- a dozen of blender users are ready to donate to this project as a consideration sign.
- the Demonware firm is supporting this project by giving 2 weeks of paid “free time” to Eman for code cleaning
*feedback from Eman:
"Hello all,
Quick update on the progress I made these past two weeks.
Here’s the TODO list I worked from:
http://wiki.blender.org/index.php/Bl…sCurvesNurbana
1. Backwards compatibility is working, libNurbana should be a complete replacement for the current NURBS
engine in Blender
http://atspeedsound.com/blender/Picture%2022.png
2. IsoLines are working (although not made pretty yet):
http://atspeedsound.com/blender/Picture%2024.png
3. Subdivision is working for endtied/clamped/open curves and surfaces:
In U: http://atspeedsound.com/blender/Picture%2025.png
In U and V http://atspeedsound.com/blender/Picture%2027.png
4. Degree Elevation and reduction is working. This allows you to change the Order of a curve or surface without
changing the shape of the surface
http://atspeedsound.com/blender/Picture%2028.png
http://atspeedsound.com/blender/Picture%2030.png
5. Hamed Zaghaghi has made weight editing use the same mechanism as tilt and radius, making it much more
user friendly:
http://atspeedsound.com/blender/weight.png
6. Both Ideasman/Campbell and Twingy/Justin have also started to contribute to this project.
It’s all looking good.
If people want to check out and build the nurbs/ branch, feeback and bug reports would be really appreciated.
thanks!"
-Emmanuel
IMPORTANT: the donations will start soon: if you want to pledge donations to show interest to the coders, please leave an name and an amount here (it does not have to be big amounts, especially with the current state of the economy!!) and the blog will be updated:
Money is not everything: you can also save time to the developpers by reporting bugs.
If bare report is better than nothing, consider a detailled bug report as it speeds up the debugging process and it is greatly appreciate by the coder: this is really quick if you have previous experience with compiling.
IamInnocent has kindly detailled the procedure:
The procedure is not something I invented : it comes straight from the recommendations on the bug tracker page.
First of all one must look if the bug was reported.
If it was then try to reproduce it using the files the reporter provided and following the procedure he/she indicates.
If the bug was not reported :
Installing gdb is trivial and I won’t bother you with that.
Using it is, for us bug trackers, also extremely simple:
- first Blender must be compiled with the BF_DEBUG=1 flag so it will include some debug information; the time to build will be longer;
- then we start gdb this way, inside a treminal, console, anything that has a command line:
gdb -silent --args <path-to-folder-where-blender-is>/blender -d
‘-silent’ is so gdb won’t brag about its ancestry
‘–args’ stands for arguments and, with that option, the ‘-d’ switch of Blender won’t choke gdb
that ‘-d’ switch makes Blender output plenty of useful information to the console.
So, you’ll get this gdb prompt:
(gdb)
Just type : run
and gdb will run Blender as a child process of itself.
Do your things, starting by loading the factory setting in the File menu (very important)
Save a lot so you’ll have a file as near as possible to the moment the problem arises
Once the problem has happened take a screenshot.
If Blender crashed go back to the command line and use the backtrace command. Something like ‘bt -20’ should do as it will output the last 20 lines of the log. Do a trace only if Blender crashed. Don’t be surprised if Blender doesn’t shut down after the crash : gdb, as its parent, keeps it alive as a zombie and as such Blender is waiting for its parent to put it to rest.
If Blender hasn’t crashed there won’t be a trace available so don’t bother with the ‘bt’ command. Just go back to the command line and terminate Blender with the Ctrl-C command of gdb. It will survive as a zombie then too, until gdb is shut down itself with the Ctrl-D command.
Copy the information the -d switch produced (and eventualy the information that ‘bt’ produced) in a text file and save.
Join the documents to your report here with a description of each step that need to be repeated to reproduce the bug.
)
