HippoPlayer v2.48

[AmiClassic]

Thank you very much, that's what I meant. All source packages contain full executable version

[AmiClassic]

I don't use scopes on a daily basis, but recently while setting up Hippo I noticed a strange effect: Hippo_scopes

As you can see in video, last good (for me) version is 2.48. Besides me, has anyone else had this problem? I have a heavily patched WB, so it may be fault of some patch?

[Shaytan]

Originally Posted by AmiClassic

I don't use scopes on a daily basis, but recently while setting up Hippo I noticed a strange effect: Hippo_scopes

As you can see in video, last good (for me) version is 2.48. Besides me, has anyone else had this problem? I have a heavily patched WB, so it may be fault of some patch?

I had the same problem and in my case it was related to the command "C:CyberBugFix" in my startup-sequence.

By disabling it the scopes now work correctly.

[AmiClassic]

I disable CBF but still the same.
I don't want to turn off anything in my s-s, so I will live without scopes or back to 2.48

[koobo]

Originally Posted by AmiClassic

I don't use scopes on a daily basis, but recently while setting up Hippo I noticed a strange effect: Hippo_scopes

As you can see in video, last good (for me) version is 2.48. Besides me, has anyone else had this problem? I have a heavily patched WB, so it may be fault of some patch?

Looks like the blitter is not working. Which blitter related patches are you using?

[AmiClassic]

I think only FBlit may be messing something up, but disabling it don't improve situation.
Version 2.48 don't use Blitter, or does it use differently?

[koobo]

Originally Posted by AmiClassic

I think only FBlit may be messing something up, but disabling it don't improve situation.
Version 2.48 don't use Blitter, or does it use differently?

I checked it and it allocates the scope draw buffer with AllocRast instead of AllocMem. This is only relevant change I can think of. Might be that some patch has modified AllocRast to allocate non-chip memory. I will attempt a fix for the next version!

[DisasterIncarna]

Using a heavy patched OS3.2 on FS-UAE/WinUAE and on a FPGA/Chameleon64 V2, heres my "extra stuff" and a vid showing a normal scope effect on latest hippo update.

[ Show youtube player ]

All My Extra Patches/Addons For Use In FS-UAE/WinUAE OS3.2.1

In Startup-Sequence or User-Startup

SaferPatches
PatchControl
CopyMEMAIO
NoMoreDiv0
BlazeWCP
MinStack
FBlit (Only When Not Using RTG)
MCP
TitleShadow
VisualPrefs
Birdie
OutLineIconText
MemTrailer
VBRControl
StringSnip
TrueMultiAssigns
Executive

In WBStartup

AssignWedge
ASyncWB
AutoArrangeIcons
AutoUpdateWB
BarClock
DefaultIcons
FreeWheel
LimpidClock
MagicMenu
ModePro
OpenParent
PatchWB
ReKeyIt
Snapper
StartPatchWB
SmartWin
StartRC
StormScreen
SwazInfo
Toolmanager (2x)
ToolsDaemon
WBDock
WarpWB
WindowToFront

[AmiClassic]

I on Amiga don't have RTG, so I don't need to emulate it. Would you be able to check it without RTG?

I was wondering why on the same config version 2.48 works normally and 2.49 and onwards does not. Koobo has already explained difference and if it can be corrected it's fine, if it doesn't work you can consider my problem gone. I don't see the point of dredging up Hippo for one extreme case.

I only use BigScope and would love to see a refreshed version of it

P.S. My WB is 3.1
P.S.2 I see that PatterScope still has a problem with fonts

[DisasterIncarna]

OS3.2.1, Emulated, Zorro/Gfx/RTG Disabled.

[ Show youtube player ]

Lets also ignore the fact the video is utterly silent because i recorded my monitor output when i was wearing my arctis1 wireless headset and recorded sweet nothing audio wise.

[DisasterIncarna]

whatever your case it, either hippo or something else, it might be worth finding the cause as it may affect more than hippo and can be worth tracking down, which is often a lenghly process but nice when you get the eventual AHA!!! moment when you find the issue.

[AmiClassic]

Thanks for test.
Perhaps it works well on 3.2.1?
We'll see what Koobo can do.

[DisasterIncarna]

Originally Posted by AmiClassic

Thanks for test.
Perhaps it works well on 3.2.1?
We'll see what Koobo can do.

yeah or when more users of 3.1 report a similar issue, just a waiting game for confirmation.

[Channel-Z]

@DisasterIncarna

What RTG sw are you using is it P96? if so fblit and ftext are not compatible with p96 and will cause all sorts of unexplainable graphical issues with other programs. Try disabling when using P96 and see if the issue goes away.

[koobo]

Originally Posted by AmiClassic

P.S.2 I see that PatterScope still has a problem with fonts

I think it was v2.49 where I added a stricter check so that it will just display nothing if the font is unsuitable. It will first try the font set in prefs and then the topaz font.

I'm aware that there are patches to hack topaz but that's a bit silly since it is one of the constants of the universe

[DisasterIncarna]

Originally Posted by SnoopDOS

@DisasterIncarna

What RTG sw are you using is it P96? if so fblit and ftext are not compatible with p96 and will cause all sorts of unexplainable graphical issues with other programs. Try disabling when using P96 and see if the issue goes away.

Yes, P96, my startup sequence detects RTG and skips over running FBlit/etc if RTG is present, it only runs for non RTG, i ran test with and without RTG and my scopes look fine.

I'm not the one with the gfx weirdness issue btw, its @AmiClassic who is having issues, he also does not have RTG

[DisasterIncarna]

Originally Posted by koobo

I think it was v2.49 where I added a stricter check so that it will just display nothing if the font is unsuitable. It will first try the font set in prefs and then the topaz font.

I'm aware that there are patches to hack topaz but that's a bit silly since it is one of the constants of the universe

good catch both of you, i forgot i had NoTopaz patch enabled in MCP Prefs, disabled that just now

[spotUP]

Try to remove blazewcp?

[DisasterIncarna]

Originally Posted by spoUP

Try to remove blazewcp?

im the 1 with that patch and im not the one with the issue

[AmiClassic]

I haven't used BlazeWCP for a long time.

This morning I was able to determine what was causing problem with scopes. Solution was to disable FBlit and CyberBugFix at the same time. Such a situation did not satisfy me, because I was losing about 700kb CHIP

Koobo has already solved this problem and in upcoming HiP version scopes work perfectly