@Mechanic

there was an initiative to fix warp3d that has been answered in a way that it was welcome only if this would exclude os3.x/68k support. i am not going to talk about it here, but worth to mention, that people involved with it help also with or make their software available on os4. warp3d licence is worded in such a way it cant become a common standard. the sources are not available. all this in course of time led to that i personally have given up and instead got engaged with aros. it is my personal choice. im not trying to scare others from contributing to os4, on the contrary.

@HammerD
Quote:

How about an update on your two interesting projects, MUI-OWB and MUI-MPlayer?

If only i be an os4betatester, and have access to post info on the hyperion blog, i will have write nice article about our MUI updates :) So , while i am plain user, i only can ask other developers to write info which closed from eyes.

Related to fab's ports on os4: MUI-OWB just wait for update3 and its ready, and mui-mplayer are on half stage and will want update3 as well :)

ps. check pm plz

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@ddni
Quote:

It is a shame that people cant say thanks for what is here, rather than complain about what is coming...

People do love to complain about anything and everything.

I'm still glad I started up the blog. Without it you'd get the usual random postings in web forums from random people. With the blog you at least know it is somebody actually working on AmigaOS and it is all in one place.

One thing is certain. Darren is super excited about AmigaOS 4.x on the classic and does everything in his power to keep the project alive. Without his efforts there would be no Classic release right now. I think we should cut him a little slack.

_________________
ExecSG Team Lead

@thellier

Thanks for the patch

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@ssolie

The blog is definately a good thing, keep it up.

_________________
gtmooya's blog

@ssolie

Quote:

ssolie wrote: I'm still glad I started up the blog.

As am I.

As for cutting people slack..............I can do that,,,,,, as the official Slacker around here.

(Yes dear, I'm busy thinking about your curtains right now.( sheeesh))

@ssolie

The blog was definately a good idea and is really appreciated.

_________________
A600 OS3.1 ACA620 | '030 A1200 OS3.5 | µA1-C 750GX OS4.1 | SAM460 OS4.1 | '040 A3000 OS2.1 | Christian Aid |

+ Infinity for the Blog

_________________
Raptor BlackBird (awaiting a Miggy like OS)
Amiga 4000 3.9 / Pegasos II 4.1 F.E.

@thellier

Do you get the impression the W3D source / dest blend enumerations were originally the same as those in the MIniGL implementation then diverged at some point? If they were, it might explain why said values are getting passed in.

Quote:

* patch: BlitzQuake/MiniGL use SetBlendMode but forget to activate with SetState() the blending */ SetState(context,W3D_BLENDING,TRUE); [...]

That bothers me a bit. From an API behaviour expectation, you should definitely be able to change the blend mode whether or not the blending state is currently enabled or not, it should just take effect the next time the state is enabled. It shouldn't have to turn it on for you (which I realise is the point of the patch).

Something like this should probably be an environment setting so that the behaviour is not hard coded in to the library.

Last edited by Karlos on 14-Jun-2011 at 10:41 PM.

_________________
Doing stupid things for fun...

>be able to change the blend mode whether or not the blending state is currently enabled or not
@Karlos
Yes i agree
In fact the patch in Wazp3D is a few more smart:

struct WAZP3D_context *WC=context->driver;

if(!WC->CallSetBlending)
SetState(context,W3D_BLENDING,TRUE);

with WC->CallSetBlending setted to FALSE at startup

and set to TRUE here
ULONG W3D_SetState(W3D_Context *context, ULONG state, ULONG action)
{
struct WAZP3D_context *WC=context->driver;

if(state==W3D_BLENDING)
WC->CallSetBlending=TRUE;

Like you told Warp3D/MiniGL often poke the w3d-context instead of calling the Warp3D function :-/


Note: you can make a quick search in Wazp3D sources for the string "patch:"

Alain

@thread

New Hyperion blog entry:

AmigaOS Support Forum Launched

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

Quote:

New Hyperion blog entry:

It might also be useful to have some kind of 'feature request area', but then again that might get
messy pretty quick.

Yaii a new forum !
A good news for OS4 bug reporting and also for asking about Hyperion's games

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

Quote:

New Hyperion blog entry: AmigaOS Support Forum Launched

Excellent news! Nice work to those involved.

Quote:

AmigaOS Support Forum Launched

a VERY GOOD move!!!
Finally!
There should be links for the blog and for the forum in the Hyperion website anyway, since some people may find difficult to find them...

_________________
A1200/020+68882 - 6 MB RAM - AmigaOS 3.0

Home Recording Audio

Quote:

AmigaOS Support Forum Launched

That was unexpected, but very right and good move. Maybe communication indeed will be better now ?

@ssolie
The only one moment, is that for making account on forum working, need to wait some manual aproving by admins (which can be busy sometimes later), and will be good to have automatic account enabling. Maybe by adding in account registration serial number info ?

And for sure, as Andres say, need to put on main hyperion site somethere at top "our support forum" , so all the users will know what and where

But its all good should to say, all those official blogs and forums are right steps.

edit: through, after a while, i start to think that forums for game-support looks a bit wrong: games very old (and we have better opensource relisations already), and non shogo, non heretic2 non working normally on os4.

Last edited by kas1e on 18-Jun-2011 at 09:28 AM.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@kas1e

Quote:

games very old (and we have better opensource relisations already)

I think it's for Hyperion's own products and not for every piece of AmigaOS software.

_________________
Rock lobster bit me. My Workbench has always preferences. X1000 + AmigaOS4.1 FE
"Anyone can build a fast CPU. The trick is to build a fast system." -Seymour Cray

@Tomppeli
Quote:

I think it's for Hyperion's own products and not for every piece of AmigaOS software.

Yeah, cross the fingers for shogo and heretic2 versions for aos4 :)

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

a related support forum is good move.

@Karlos

>Do you get the impression the W3D source / dest blend enumerations were originally the same as those in the MIniGL implementation then diverged at some point? If they were, it might explain why said values are getting passed in.
No .
I only think that they only converted the src/destmodes that existed in Warp3D v4
and forgot that OpenGL can also send some other value.
It is only a "parameter is not converted nor checked" problem

Alain
Error is in MiniGL/others.c in cgl_GLBlendFunc() -> It should be like that:

switch(sfactor)
{
BLS(ZERO);
BLS(ONE);
BLS(DST_COLOR);
BLS(ONE_MINUS_DST_COLOR);
BLS(SRC_ALPHA);
BLS(ONE_MINUS_SRC_ALPHA);
BLS(DST_ALPHA);
BLS(ONE_MINUS_DST_ALPHA);
BLS(SRC_ALPHA_SATURATE);
BLS(CONSTANT_COLOR);
BLS(ONE_MINUS_CONSTANT_COLOR);
BLS(CONSTANT_ALPHA );
BLS(ONE_MINUS_CONSTANT_ALPHA);

default:
GLFlagError(context, 1, GL_INVALID_ENUM);
}

switch(dfactor)
{
BLD(ZERO);
BLD(ONE);
BLD(SRC_COLOR);
BLD(ONE_MINUS_SRC_COLOR);
BLD(SRC_ALPHA);
BLD(ONE_MINUS_SRC_ALPHA);
BLD(DST_ALPHA);
BLD(ONE_MINUS_DST_ALPHA);
BLD(CONSTANT_COLOR);
BLD(ONE_MINUS_CONSTANT_COLOR);
BLD(CONSTANT_ALPHA );
BLD(ONE_MINUS_CONSTANT_ALPHA);
default:
GLFlagError(context, 1, GL_INVALID_ENUM);
}