Guild of Writers

Hoikas has found a solution for wavesets not showing up on older graphics cards here in the GoMa forums. The trick is using geostate settings, which are disabled by default. This should make any graphics card that is capable of drawing wavesets in (most of) Cyan's ages draw wavesets in yours as well.

I have successfully tested this method with Prad. Now it is up to you to fix your wavesets, because you do want everyone to admire them, right? And as a bonus geostate adds a nice up/down water movement effect. So what are you waiting for?

But... what are good geostate settings? I wish I knew. I found that it depends a lot on your other waveset settings. These are the settings I use for Prad.

Code: Select all

            geostate:
                maxlen: 6.25
                minlen: 6.0
                ampoverlen: 0.001
                chop: 0.0
                angledev: 1


I believe PyPRP should not default geostate to 0. I do realize though that it takes a lot of trial and error to find good defaults. So it would be nice if we could come up with suitable settings here.

Please experiment with this and report your findings.

The only problem I see is that if the writer has working wavesets without geostate; how will he/she know what to set it to?

It doesn't matter what you set it to as long as you get rid of the default zeros.

It does have a visual effect. You'll see. That is what you tweak until you like what it does. And if you don't like it at all you can give it a minimal effect (I think that should be the default).

Of course the easiest solution is to upgrade your video card.

This is what A LOT of people did when MOUL came back, including me

He's right though. I do consider this a bug in PyPRP. Optimal defaults are a desirable feature. This will be fixed in the future. (when exactly, is up to the universe >.>)

Grogyan wrote:Of course the easiest solution is to upgrade your video card.

This is what A LOT of people did when MOUL came back, including me

I did, but you cannot force people to upgrade their hardware. Keep in mind that not everyone can afford that. But more importantly... <repeat>If Cyan's wavesets work on a particular video card so should UCC wavesets.</repeat>

Believe me, there are still many people affected by this bug. Just go over to GoMa and read the test reports. And I can assure you that it is extremely frustrating.

My new computer displays all wavesets fine but I will keep the old one to hunt down this bug. So if anyone wants me to do a visibility test just let me know.

er.....WHERE in the waveset script do I stick this?

Would it be after Textstate? (that makes the most sense to me.......)

andylegate wrote:er.....WHERE in the waveset script do I stick this?

Would it be after Textstate? (that makes the most sense to me.......)

That would be a good spot but in fact order doesn't matter for most alcscripts.

Okay that's where I put it......

Mmmmm......last time I just "stuck it any old where" I spent hours chasing my tail because it had a indent problem.....hehehe....

This is an amazing fix for this problem that has been dogging fan-made wavesets since their implementation into PyPRP. GJ Hoikas & D'Lanor.