GoW PyPRP 1.6.0 Beta 2 released

[Christian Walther]

Doing a check out instead of an update bypasses the bad revisions.
- Right-click local svn root folder
- Choose Tortoise SVN > Repo-browser
- Right-click the root folder in the Repo-browser > http://svn.guildofwriters.com/pyprp
- Choose Checkout > OK > confirm OK

Creating a new folder and performing a fresh checkout on it also works as I have just verified. This is probably an easier method.

Confirmed, your first method works and preserves local modifications. Doing a fresh checkout can be inconvenient if you have local modifications.

I've found two more approaches that work, for the sake of completeness:

• Excluding the troublesome folder from the working copy (if you don't mind having it excluded permanently, since trying to get it back gets you the same error again):
  
  1. Update until TortoiseSVN gets stuck on branches\1.6\Wiki Excerpt\w\skins\common\wikibits.js?97.
  2. Go to branches\1.6\Wiki Excerpt\w\skins and right-click on common.
  3. Choose TortoiseSVN > Update to revision...
  4. Leave Revision at HEAD, change Update Depth to Exclude, and click OK. The common folder is removed.
  5. Updating the whole tree again should work now without trying to restore that folder.
• Some surgery that restores your working copy into a fully functional and complete condition:
  
  1. Update until TortoiseSVN gets stuck on branches\1.6\Wiki Excerpt\w\skins\common\wikibits.js?97.
  2. Go to branches\1.6\Wiki Excerpt\w\skins and delete the common folder (without telling SVN).
  3. Using the repo browser, check its newest revision out again to the same place.
  4. Update the whole tree again to collect any leftovers.

I am not sure why this happens because my ripples and footprints are still fine.

It probably depends on the order in which you initially ran PyPRP scripts, determining where import cycles are broken. That's what you get for using from something import * in modules.

I haven't tested it yet, but Hoikas' solution looks right to me. It also needs to be applied to a few more lines in that file.

[Tsar Hoikas]

Yeah, I saw that myself but, as I say, am unable to test anything right now, so I didn't do the fixing myself. Just wanted the solution to be known.

[Jamey]

Ok, I just downloaded the new PyPRP scripts, and I did NOT replace the scripts in my 'scripts' folder within my .blender folder.

Instead, I did what I did for an earlier version of PyPRP, I created an entirely new folder named PYPRP 1.6 Beta, which had a folder within that called PyPRP 1.6, which contained the scripts.

Upon exporting, I got this:

Code: Select all

Compiled with Python version 2.5.2.
Checking for installed Python... got it!
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "c:\Program Files\Blender Foundation\Blender\.blender\PyPRP 1.6 Beta\PyPR
P 1.6\prp_Export.py", line 50, in <module>
    from PyPRP import prp_Config
ImportError: No module named PyPRP
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "c:\Program Files\Blender Foundation\Blender\.blender\PyPRP 1.6 Beta\PyPR
P 1.6\prp_Export.py", line 50, in <module>
    from PyPRP import prp_Config
ImportError: No module named PyPRP


I have absolutely no idea what went wrong Hope I didn't make a huge mess...

[D'Lanor]

I have absolutely no idea what went wrong

I think you do...

I did NOT replace the scripts in my 'scripts' folder within my .blender folder.

That is what went wrong. Why don't you just follow the instructions and install the PyPRP folder within the Blender scripts folder?

[Jamey]

They have to be installed within the scripts folder? Oh....my bad, sorry

The reason I gave this method a shot is that I figured it would work since I had used a different folder for PyPRP version 0.5, and that worked. I also wanted to make sure if something broke in one of my ages with the newest release, I could just go back to 1.5 to export the ages since I would not have replaced those files.

Edit: OK, I replaced the current scripts in my scripts folder with the 1.6 as I would with other releases, and I'm getting the same error...

Do I need to just replace the current scripts as I would usually do (which worked before with previous releases), or do I need to throw the whole 1.6 folder in there with the 1.5 scripts?

...I know nothing about how this stuff works, which is probably why I'm where I'm at

[D'Lanor]

From the wiki:

PyPRP 1.6 Beta

If you have a previous version of PyPRP installed, uninstall it by removing all files starting with prp_ (or alc and uruprp_ for even older versions) from your Blender scripts folder. Unzip the file and move the PyPRP folder (the whole folder, not the files in it – this has changed from previous versions) into the Blender scripts folder.

[Jamey]

got it! Thank you for your help D'Lanor!

[Christian Walther]

Jamey, since the instructions obviously failed to either get your attention or explain things properly, do you have any suggestions on how to improve that? Is there anything we could have done differently so that you wouldn't have run into that problem?

[Christian Walther]

NameError: global name 'hsGMatState' is not defined

As I suspected: the error occurs when, in one Blender session, you first run the Wizards script and then the Export script. It does not occur when you run the Export script first. (I guess that was also the reason it worked for you, Whilyam, after removing the footprint code - you can put it back and it should still work. Otherwise it would also have failed on the ripples.)

There may be other problems of that kind. If you run into them, please report them, even though you can easily work around them by quitting and restarting Blender and trying the export again without running any other PyPRP scripts before.

A tested fix is now committed to the 1.6 branch (r435). We can merge all beta fixes to the trunk in one go at the end, unless anybody is working on the trunk and wants them immediately.

[Jamey]

Jamey, since the instructions obviously failed to either get your attention or explain things properly, do you have any suggestions on how to improve that? Is there anything we could have done differently so that you wouldn't have run into that problem?

I've underlined my case

Most of it was my fault though. Here is what happened; I wanted to install 1.6 and at the same time, have a backup of 1.5 in case the release of 1.6 caused anything to break in my ages. This is why I saved 1.6 in a place other than the scripts folder, like I did for other PyPRP releases. Now at the time, I did not know that I needed to put the whole folder in this time rather than just throw just the scripts in there mainly because;

1. I was rushing this whole process trying to get it done
2. Thinking that installing 1.6 would work exactly like the other releases like 1.5.

When D'Lanor showed me the Wiki, which I missed, Everything made complete sense.

So yeah, most of it was my fault