Guys, if there is such a bug it would be good to publish a warning about it. I've been using that feature, and this might explain some weird bugs I've been having.
Here's a script that could make life easier for automating the compilation process. This will compile all prcs in a folder to corresponding uofs. Just drop it in your project folder and run it before importing with PrpExplorer. I initially wrote it in order to simplify Andy's "Snow in your Age" tutorial, but I never got access to the Maintainer's forum so I forgot about it.
- Code: Select all
@echo off
REM compile all PRC files in folder into UOF files
REM edit the following path for your own installation
rem libfolder is the libPlasma folder
set libfolder="D:\Uru\Utils\LibPlasma"
echo Compiling PRC files from current folder
del *.uof
for %%i in (*.prc) do %libfolder%\prcc.exe %%i -v pots -o %%~ni.uof
set libfolder=
echo Done.
pause
I'm too stupid to write utilities using libPlasma (and i don't have a c++ compiler), but I can think of two utilities that would be quite useful:
- a more granular prdcd which would export a specific object instead of the whole prp.
Something like "prcdc [options] filename [plKey Name] [plKey Type]"
Example: "prcdc -o D:\Uru\project1\so_Lamp2.prc D:\Uru\dat\tutorial01_District_mainRoom.prp Lamp2 plSceneObject"
- an object importer (similar to the import function in PrpExplorer).
Something like "prcimport [options] prpfilename prcfilename"
Example: "prcimport D:\Uru\dat\tutorial01_District_mainRoom.prp D:\Uru\project1\so_Lamp2.prc"
This one would be, actually, a stand-alone version of the saving routine Paradox is working on.
The good thing about this scheme is it would bypass the compilation process entirely.
So the process for modifying an Age would be: export needed objects using prcdc, edit the prc files, add some new ones if needed, import back all prcs using a script. This would also make it a lot easier to distribute new and modified content.