#PAR 1.50
33 messages in this thread
PAR 1.50 has been posted to the Hware/OpSys/Video library. It is the PAL and
NTSC versions.
Brick,
Could you please tell us of the changes in 1.5. Always like to know what I'm
getting into before jumping in. <g>
Ralph
Ralph:
PAR.EXE 1.5 is great! It is not a beta version, but a shipping release. I
found that renaming your old PAR directory to something else and then just
doing a full install works fine.
Greg Pyros
where do I get PAR 1.5???
thanks Paul Boyd
Paul:
>> where do I get PAR 1.5???
Either here on ASOFT or the DPS BBS!
Greg Pyros
I have a few more questions: Do I need to reformat my drive? Will 1.5 play ANI
files created with 1.09 Are there any NEW features to 1.5 What will 1.5 give me
that the other version did not? (I just received my PAR 2 weeks ago and I have
not had any problems….yet)
Thanks
Paul Boyd
Paul:
>> Do I need to reformat my drive? [to upgrade to 1.5 PAR.EXE]
nope.
>> Will 1.5 play ANI files created with 1.09?
yup.
>> Are there any NEW features to 1.5?
Depends on where you are coming from – are you running 1.0 or one of the beta
versions that has been floating around the last year?
There is a readme with the new version detailing the changes.
>> I just received my PAR 2 weeks ago and I have not had any problems.
I'd just download and upgrade. Make a new directory, just in case, and make
sure you reboot between running the new and old to make sure that your
initialization program and drivers are for the proper version!
Greg Pyros
I just downloaded the new 1.5 ver. and followed Greg's suggestion of renaming
my old DPSPAR directory as a backup. I used windows File Manager for this.
The new installation went OK and I had a third of my Par drive loaded with
stuff that could be trashed if necessary. I allowed the install to modify my
autoexec.bat but remed it out before rebooting as it was similar to my startup
batch files for the PAR. I launched the 1.5 PAR with the original startup bats
and the new look was a surprise over the 1.30b ver I had used. Everything
worked and didn't require reformatting. Now where's the Windows driver's.
Guess these will be delayed. Need them for Premier 4.0!
If you are having problems with files, then you may want to format the drive
and start over. The 1.50 version is definetly more robust at handling file
problems but only if it can catch them right away.
Brick
Brick:
I've noticed (and I _think_ 1.3x did this, too) that when you've got import set
to "ANIM", and you hilight an ANI file and click the IMPORT button, the type
button always switches to "STILL". It's not a problem, as the file still
imports AS an ANI, but you have to remember to switch it back for the next
time.
Also, (and this has DEFINITELY happened since 1.3x), even though I've 3DS set
to field-order=1 (the default), I have to set the PAR software to field-order=2
— even though this is the opposite of what the docs state. Otherwise, I get
the jiggly, flashing problems of having the fields backwards.
You mentioned before that you were adding a scripting feature… is that for
2.0? Any time frame estimates? What about the MCI drivers?
Thanks,
Dave
Dave:
/_______________________From your message________________________\\
I've noticed (and I _think_ 1.3x did this, too) that when you've got import
set to "ANIM", and you hilight an ANI file and click the IMPORT button, the
type button always switches to "STILL".
__________________________________________________________________
I just installed 1.50 this afternoon and had the exact same thing happen to me.
It gave me a quick heart palpitation and I clicked on ABORT. Of course the
entire
ani file imported fine but I expected to see a pile o' .stl files.
Bob
>>a quick heart palpitation…
I know EXACTLY what you mean, though for me, it's more like it jumps up into my
throat, and there's this tiny and thin little scream in my head:
"Noooooooooooo!".
Um, maybe I should get some counseling, hm? <g>
Dave
Dave:
>> Um, maybe I should get some counseling, hm? <g>
No, too late. You're a fully grown mutant, no hope of ever
recovering. Live with it.
David: <tiny and thin little scream> eeeeeeeeeeeeeeeeeeeek <LOL> jeffrey
I can also account for having to switch to field order = 2 for TGAs
from 3D Studio. I thought this seemed odd at the time, but it
worked!
Dave, the Field Order issue is really a matter of a difference of
terms. Gary uses 0 and 1, and the DPS folks are using 1 and 2. Since
the default in 3DS.set is 1, this equates to 2 in the DPS software.
If they are both set to one, there will be problems, as you have
seen.
-Alan
While I can certainly accept that explanation, the DPS readme doc's
specifically state that "The standard order (1) for 3D Studio and
Crystal Topaz. Order 2 is for importing field rendered files from
other platforms such as the Amiga and SGI." Even if the doc's were
just wrong, the software/install shouldn't default to the order for
another (non-DOS) platform!
I agree totally, Dave, and I coulda' swore BrickE said he was gonna change that
default (and the docs) way back when I was beta-ing the first release of the
software and I called it to his attention. Hmmm…I'll ask him about that when
we speak next.
-Alan
>> PAR.EXE 1.5 is great! It is not a beta version, but a shipping release. I
I'll check it out.
Ralph
New 1.50 changes
There are many, many changes that have been made since the 1.09 release.
Those of you that have been using the betas (and I can't thank you enough for
your patience and feedback) will be familar with all the changes. the best
thing to do is to send in your registration card, and make sure you are in our
database, we will make available to 1.09 users a new manual at no charge. The
new manual covers all the changes, and new features as well as extensions to
the older manual. I think you will like the new manual a lot.
Highlights for 1.50
New GUI
Gui changed to be more consistant and more appealing (we think)
New PARDRV
Changes to PARDRV to better handle export and import files
More robust file checking
896 frame limit removed..
Deleteing projects fixed
numerous inconsistancies fixed
added play N grab function
on and on and on…
Brick,
Thanks for the info on 1.50. Actually I installed it yesterday. I figured
you must of re-did the memory management/requirment in Pardrv someway, as
3DS and Windows had a problem UNTIL I re-optimized Qemm. All is OK
now… nice new interface look.
Ralph
Well, I sent in my registration 2 weeks ago, can you send me my new manual?
Paul Boyd Phoenix
Just to get it straight, I have 3DS field order set to 1, to import to thr
PAR drive I set the fields to, (A) 0 ,(B) 1 ,(C)2 ,(D) None of the above.
PMJI, but with field order in 3DS=1, the numbers you use for the PAR are
different depending on where they are set:
in PARDRV = 1
in PAR.EXE = 2
thanks
Thanks for your great support, have installed it already and looks great hope
the backup problem is solved will check that next week.
Christophe
RE: backup problem..
The problem is solved.. Hope you like the PAL/NTSC installation also, we did
that just for you <g>
Hi Brick,
<<putting in PAR/NTSC in 1.50>>
And maybe also a little bit for me. But can you get into the problem that
sometimes the PAR.EXE comes up with the PAR-project directories in the
DOS-window. And my compliments for the new join,…. fast..faster..fastest,
and you know i had everything saved on disk <896 and reserved a night
for joining, but after 10 minutes i could go out for dinner.
Thanx
Theo
I had hoped that 1.50 also solved my problem of RAZORPRO not been
able to acces the PAR-slave and when writing to the PAR destroying everyhthing
on it. But i have to chase the In:Sync people for this !?
>>The problem is solved.. Hope you like the PAL/NTSC installation also, we did
that just for you <g><<
Wow I'm starting to feel myself become important.
Or should I say I'm embarrased.
BTW thanks, a lot of PAL users will be pleased I have contact with some on and
of CIS.
Christophe
Minor quibble – with 1.27b I was able to simply pick up where I left
off in importing files with the same prefix and a frame number that
immediately followed the last loaded on the PAR. For some reason, 1.3
will no longer import the next file in the sequence – but gives me an
error message to the effect that it cannot import the file. When I
switched back to the older beta, "voila" – imported fine. Maybe it's
because I began this saga using the old software????
TIA for your help.
By the way, new interface definitely the 90's look. Many improvements,
even over the 1.27 beta.