Blender scripts update

[NaN]

I've fixed some bugs in the import/export scripts, especially the annoying texture coordinates issue with double-sided faces. Testers are welcome.
http://svn.vdrift.net/viewvc.cgi/trunk/t...VDrift+Art

By the way is anybody using the old export-joe-0.3.py and export-all-joe-0.3.py?

[portets]

will test soon.

By the way is anybody using the old export-joe-0.3.py and export-all-joe-0.3.py?

maybe move them to an "Old" subdirectory within their current directory?

[alex25]

I've fixed some bugs in the import/export scripts, especially the annoying texture coordinates issue with double-sided faces. Testers are welcome.

so i see you reverted my changes to set the filename from joename and instead use the truncate blender meshname. this makes it much harder to work on tracks but i guess since you intend to do such work yourself from now on, good luck! btw, you forgot to remove mesh.properties['joename'] = name from tools/vdrift.py which is now useless.

--alex--

[NaN]

Unfortunately, your changes broke the exporter and I've been too lazy to fix them. Do you mind to try the latest revision to see if it works for you?

i guess since you intend to do such work yourself from now on, good luck

Well, I've pretty much given up expecting any help related to track data modifications.

[alex25]

Unfortunately, your changes broke the exporter and I've been too lazy to fix them. Do you mind to try the latest revision to see if it works for you?

what do you mean it broke the exporter? i've been using it on various tracks just fine. it doesn't prompt for a name, it just saves using the original name but that was the whole fucking idea. would you care to elaborate on how exactly my changes broke the exporter?

i guess since you intend to do such work yourself from now on, good luck

Well, I've pretty much given up expecting any help related to track data modifications.

what exactly is this supposed to mean? i've contributed a lot of tracks to vdrift and i keep improving them. how many have you contributed?

--alex--

[NaN]

what do you mean it broke the exporter? i've been using it on various tracks just fine. it doesn't prompt for a name, it just saves using the original name but that was the whole fucking idea. would you care to elaborate on how exactly my changes broke the exporter?

Ever tried to export a non-imported mesh?

trying to get the seat exported, and i get an error.
here's the output:

Traceback (most recent call last):
File "/home/zimluura/.blender/scripts/export-joe.py", line 30, in save_joe
filename = mesh.properties['joename']
KeyError: 'key not in subgroup dict'

tried on the seat, and triangulated cubes. i am typing a filename. tried with almost all the export.py files in there, but most recently with just export-joe.py, import-joe.py, and vdrift.py

any ideas?

i've contributed a lot of tracks to vdrift and i keep improving them. how many have you contributed?

Do you mind to compile a list of the tracks you've contributed? The sourceforge logs are only reaching till 2007.

[alex25]

Ever tried to export a non-imported mesh?

trying to get the seat exported, and i get an error.
here's the output:

Traceback (most recent call last):
File "/home/zimluura/.blender/scripts/export-joe.py", line 30, in save_joe
filename = mesh.properties['joename']
KeyError: 'key not in subgroup dict'

tried on the seat, and triangulated cubes. i am typing a filename. tried with almost all the export.py files in there, but most recently with just export-joe.py, import-joe.py, and vdrift.py

any ideas?

no i haven't but the solution should have been simple (set the filename only if the joename property is defined):

Code:

if mesh.properties['joename'] != '' :
  filename = mesh.properties['joename']

or something like that, not really sure on the python syntax.

Do you mind to compile a list of the tracks you've contributed? The sourceforge logs are only reaching till 2007.

ok i'll humour you:
a1ring, bahrain, barcelona, brands, charade70, detroit88, dijon, estoril88, fuji, hockenheim, hungaroring06, imola2005, interlagos, jarama, jerez88, kyalami, lemans, magny, melbourne, monaco88, montreal, monza88, mosport, pau, paulricard88, ring2007, sepang, singapore, spa2008, suzuka2005, vir, zandvoort

--alex--

[alex25]

apparently the solution is:

Code:

if "joename" in mesh.properties:
          filename = mesh.properties['joename']

if the joename property exists then it just uses that name, otherwise it uses whatever name you give it and in either case it seems to work fine.
can we have this code added back to the exporter?

--alex--

[NaN]

can we have this code added back to the exporter?

Try rev 169.

ok i'll humour you: ...

Thanks for the list. It will certainly help me to re-evaluate my involvement into VDrift given our personal differences.

[alex25]

Thanks for the list. It will certainly help me to re-evaluate my involvement into VDrift given our personal differences.

i have nothing personal against you, it's just a difference in styles. when i join a project i first make sure i know what's going on and try very hard not to step on anybody's toes in my ignorance. then i just contribute as much as i can, and I don't really care about recognition or anything else. i contribute to this project mostly for my personal enjoyment but to also give something back. anyway, not sure why the number of tracks i contributed to vdrift should decide your involvement in vdrift, but that's your choice.

--alex--

[fudje]

Is anyone using the Blender 2.5x betas already?

[NaN]

try very hard not to step on anybody's toes in my ignorance

I've yet to see a project without having bugs, regressions or changing functionality during its development. It just doesn't make any sense to me, sorry.

anyway, not sure why the number of tracks i contributed to vdrift should decide your involvement in vdrift

Let's say I had some code to support track object instances and rigid bodies. But it would require rather extensive changes to the track files breaking your current workflow and eventually introducing some regressions. I don't see it happen given our differing points of view.

[alex25]

Let's say I had some code to support track object instances and rigid bodies. But it would require rather extensive changes to the track files breaking your current workflow and eventually introducing some regressions. I don't see it happen given our differing points of view.

how about we try to take care of the current regressions first, like the way the car bounces all over the place when it hits even a little bump, adding back support for the rolling coefficients, etc.? the last few tracks i checked in have no surface coefficients because the car (at least the F1-02 which i like to use) behaves very unnaturally on every track. pau, with the high curbs, it's almost undrivable. i have no problems reworking the tracks as long as we are moving towards a definite goal and eventually get the new features to work. i really appreciate all the work you've done but a lot of the new stuff is not quite working yet (and it hasn't been working for a while) and it causes definite regressions. i don't think adding even more half-working features is a good idea, but that's really not my call to make. either way, we'll figure something out.

--alex--

[charlieg]

Thanks for the list. It will certainly help me to re-evaluate my involvement into VDrift given our personal differences.

...

Let's say I had some code to support track object instances and rigid bodies. But it would require rather extensive changes to the track files breaking your current workflow and eventually introducing some regressions. I don't see it happen given our differing points of view..

Erm...

1. don't over-react

2. learn about branching; branch, work there, choose a single proof-of-concept track that you'll use as an example, and clearly document changes to the track format so - when ready - it's straight forward enough to bring other tracks up to speed (pun intended!)

3. ?

4. profit!

Catch my drift? Pun also intended!

I think everybody appreciates the effort you put in, and collaborate development is a skill that must be learnt and learning is not always simple. Be patient, be open to constructive criticism, and enjoy yourself.