Glitches in some demos...

Hi there!

First of all, please keep in mind that I'm not good with hardware, especially in Amiga case... I just use it ^^

Well, I have problem with my little friend. Some demos, especially PPC ones and those made by TBL are acting weird.
Just look at it:

"OceanMachine" by TBL: [ Show youtube player ] (around 1:20)
"Option" by Potion: [ Show youtube player ] (around 2:00)

Can you see "corrupted" graphics? I don't know what's going on...

I have:
- A1200 tower
- kickstart 3.0
- BPPC 603e/160/040/33 (overcloked from 25 by previous owner)
- BVision
- 96 MB RAM
- OS 3.5

The problem occures either with WB loaded and w/o startup-sequence.

I have made some tests:
FPU Test = everything OK
Memory Test 1 = everything OK
Mempry Test 2 = CHIP memory OK, but during "External Memory Test" it looks like it's doing nothing (I have waited 30 minutes and there was no action)
Memory Test 3 = errors, errors, errors...

I had also run two fractal-generators, AMountains and FlashMandel, and they both have generated images with little glitches and then have frozen entire system...

So, do you have any ideas what causes this problem and how to fix it?

[extralife]

I myself don't own a ppc, I own a 060 and TBL's ocean machine is a 060 demo, but it should be able to run on a 040 i guess, only slower, but not supposed to look like that
Could this be a library problem maybe ? I was thinking maybe u needed to update your accelerator libraries ?
Allso, if u run without startup-sequence, do u remember to run setpatch before running the TBL demo ? This is a must if u run newer aga demos before startup-sequence to patch your system
Just a couple of ideas here, as i said i know not how ppc works

[coze]

for stable PPC OS 3.x usage, you must,

install boing bags 1 & 2,
install latest 68x.libraries
install pcc.library patch (which disables onboard ppc.library and 68x.library)
install latest warp-up
install latest CGX drivers with exec.lib workarounds (don't really remember the details, but there was a patch involved in working latest CGX.library work with latest exec.lib)

until you've done these, don't bother testing anything. everything will act weird.

[Charlie]

Like coze says...

...also the BVision is a hot little card - esp the GPU. Some of the corruption could be interpreted as overheating.
Having earthed yourself have a feel of your BVision's GPU & RAM while you're running one of these demos - expect it to be quite warn, but not really hot.
If so, I'd strongly recommend getting some heat-sinks for the RAM & either an active or passive heat-sink for the GPU - depending how good the air-flow is round your BVision.

All the best.

[NovaCoder]

Originally Posted by Charlie

Like coze says...

...also the BVision is a hot little card - esp the GPU. Some of the corruption could be interpreted as overheating.
Having earthed yourself have a feel of your BVision's GPU & RAM while you're running one of these demos - expect it to be quite warn, but not really hot.
If so, I'd strongly recommend getting some heat-sinks for the RAM & either an active or passive heat-sink for the GPU - depending how good the air-flow is round your BVision.

All the best.

Would the BVision even be used by an AGA demo? I thought they were a retargeted card like the Voodoo in a Mediator?

[andreas]

@mod: how about moving this to Hardware forum? This is REAL Amiga, not emulator. The Hardware forum is almost entirely reserved for issues with the real machine. just my 2c

[StingRay]

"English Amiga Board > » Problems > prb.Demos"

Where is the problem?

[andreas]

Not really a problem, but once it's known to be a hardware problem, glitches are not only supposed to be happening when running demos, but with demanding (more recent) games as well.

[StingRay]

Originally Posted by andreas

Not really a problem, but once it's known to be a hardware problem, glitches are not only supposed to be happening when running demos, but with demanding (more recent) games as well.

Yes, once it is KNOWN. You, however, complain before it is even clear that it is a hw problem. And I fail to understand what it has to do with real Amiga/vs. emulator either.