Page 4 of 5

Re: GoW PyPRP 1.3.1

PostPosted: Sat Apr 19, 2008 10:46 pm
by Nadnerb
Ok, this may have been caused by one of the new features in the update. I put in a change shortly after the release of 1.3.1 (the second consecutive release from hell so far :() but it's possible that may have fixed the problem with the lights.

http://svn.guildofwriters.com/pyprp/tru ... Classes.py

replace that file and tell me if it works.

Re: GoW PyPRP 1.3.1

PostPosted: Sun Apr 20, 2008 8:33 am
by Aloys
That works for me!
A lamp, a sun, and an area light in my test Age working fine. Thanks for the fix. :)

Re: GoW PyPRP 1.3.1

PostPosted: Sun Apr 20, 2008 5:23 pm
by Whilyam
Works for me too. Thanks. :D

Re: GoW PyPRP 1.3.1

PostPosted: Mon Apr 21, 2008 2:17 am
by Jojon
Yaaay, that did it! *sings Brendyman's praise*

Re: GoW PyPRP 1.3.1

PostPosted: Mon Apr 21, 2008 7:01 pm
by andylegate
Can we please have the link to the trunk again, for those of us that would like to use the "bleeding edge" version? Thanks.

EDIT: I found it. http://svn.guildofwriters.com/pyprp

Still, you might want to post it again.

Re: GoW PyPRP 1.3.1

PostPosted: Thu Apr 24, 2008 8:51 am
by Goofy
ummm got a kinda problem here. I've been using version 1.3.0 for a time and have had little to no problems, but today I decided to use 1.3.1(unchanged from release) and I got the below.

Code: Select all
Compiled with Python version 2.5.
Checking for installed Python... got it!
Exporting c:\Program Files\Blender Foundation\Blender\.blender\homeage\pharts\lo
gictest.age ...
Args are e_age
['e', 'age']
Exporting age logictest
[AlcScript Parser]
Traceback (most recent call last):
  File "<string>", line 176, in open_file
  File "<string>", line 67, in export_age
  File "C:\Program Files\Blender Foundation\Blender\.blender\scripts\alc_AlcScri
pt.py", line 206, in _LoadFromBlender
    AlcScript.book = AlcScript(text)
  File "C:\Program Files\Blender Foundation\Blender\.blender\scripts\alc_AlcScri
pt.py", line 55, in __init__
    self.Read(text)
  File "C:\Program Files\Blender Foundation\Blender\.blender\scripts\alc_AlcScri
pt.py", line 67, in Read
    self.content = yaml.safe_load(text)
  File "C:\Python25\lib\site-packages\yaml\__init__.py", line 82, in safe_load
    return load(stream, SafeLoader)
  File "C:\Python25\lib\site-packages\yaml\__init__.py", line 66, in load
    return loader.get_data()
  File "C:\Python25\lib\site-packages\yaml\constructor.py", line 38, in get_data

    return self.construct_document(self.get_node())
  File "C:\Python25\lib\site-packages\yaml\composer.py", line 27, in get_node
    return self.compose_document()
  File "C:\Python25\lib\site-packages\yaml\composer.py", line 34, in compose_doc
ument
    node = self.compose_node(None, None)
  File "C:\Python25\lib\site-packages\yaml\composer.py", line 63, in compose_nod
e
    node = self.compose_mapping_node(anchor)
  File "C:\Python25\lib\site-packages\yaml\composer.py", line 106, in compose_ma
pping_node
    while not self.check_event(MappingEndEvent):
  File "C:\Python25\lib\site-packages\yaml\parser.py", line 95, in check_event
    self.current_event = self.state()
  File "C:\Python25\lib\site-packages\yaml\parser.py", line 425, in parse_block_
mapping_key
    if self.check_token(KeyToken):
  File "C:\Python25\lib\site-packages\yaml\scanner.py", line 116, in check_token

    self.fetch_more_tokens()
  File "C:\Python25\lib\site-packages\yaml\scanner.py", line 220, in fetch_more_
tokens
    return self.fetch_value()
  File "C:\Python25\lib\site-packages\yaml\scanner.py", line 579, in fetch_value

    self.get_mark())
yaml.scanner.ScannerError: mapping values are not allowed here
  in "<string>", line 4, column 14:
        daylength: 24.0
                 ^


Not sure what all that means. I haven't changed blender install. it's still what I had from the start. I noticed that alscript is mentioned :roll: I don't have any use for that atm so I don't have one. I also don't have any sounds atm(its just a test age.)

Is that they bug that others have talked about?

Re: GoW PyPRP 1.3.1

PostPosted: Thu Apr 24, 2008 11:46 am
by D'Lanor
No, this is a bug we did not find because we all have alcscript. Looks like you pinned down the cause too... not having an alcscript.

Edit: You should always create a book before attempting an export. That will add a default empty alcscript. Without a book PyPRP cannot handle the Blender file. Nor should it, because without a book it is technically not an Uru age.

Re: GoW PyPRP 1.3.1

PostPosted: Thu Apr 24, 2008 12:10 pm
by Goofy
well scratch what I said about not having one. Apparently I do, but its empty(no entrys) As far as I know it never had anything in it to begin with. Since I never use it at this point so never bothered to look at it. Only thing I changed was the sequence number.
Also this test age has had a book since just before 1.3.0. Its nothing complicated just a few objects w/materials and textures, lights. It exported fine with 1.3.0, but apparently something in 1.3.1 doesn't like it.

Re: GoW PyPRP 1.3.1

PostPosted: Thu Apr 24, 2008 12:34 pm
by D'Lanor
I just found that if you create a book in v 1.3.1 the alcscript is not empty. It has a line in it:

# insert AlcScript code here

What you can try is adding a short line like that. Make sure it starts with a #

Re: GoW PyPRP 1.3.1

PostPosted: Thu Apr 24, 2008 2:18 pm
by Nadnerb
Actually, you do have a book, and there is something in it. The line shown in the error log came from the yaml parser. "daylength: 24.0" is the third line in the default book file. Try looking at your book text file again, and try scrolling up this time. ;) The mapping values error is probably an indentation error in the book file.