@joerg

I'm curious as to what OWB is doing with memory, given that the requirements are so high. Right now I'm typing this in Firefox, and it's using ~32MB. With ten pages open (and browsing for a while) this can get up to 80MB. Is OWB grabbing a huge chunk of memory for itself on startup? Does it have a huge stack?

Also, how much faster would it be if SDL were dropped and the native API was used directly? It's a sizeable task, but SDL is known to add a certain amount of overhead.

BTW, does anyone know how to use the profiler with GCC?

Hans

@spotUP

Any updates?

How would you describe progress?
- Molto Allegro
- Allegro
- Poco Allegro
- Moderato
- Poco Lento
- Lento
- Molto Lento

Hans

@Rogue

I have a Radion x1300 as a PCI card. Internally it's PCI-Express, but it has a bridge. OS4 detects all that and recognizes the card too.

Hans

@NotYo

Quote:

Really? I didn't realize that this idea would be such a big problem.

Hans

@poweramiga

Quote:

Why? What's the problem with it?

Hans

This is not a suggestion for just this website, but for all Amiga related forum sites. I've already suggested it over on AW.net, and a few people think it would be nice.

The idea stems from the fact that we have several fora with similar but different specialities: Morphzone is about MorphOS; AROS-exec is about AROS; amiga.org is geared more toward classic stuff; amigaworld is geared more toward OS4; amigans.net is really focused on OS4. Many of us have interests in multiple areas.

What I think would be a good idea is to leave each forum site dedicated to it's Amiga niche, but have them all cross-link to each other. That would be friendly, and give people easy access to news and discussions regarding all systems. Many of us have accounts on AW.net, a.org, morphzone, etc. I think people would be happy with such an arrangement.

Maybe AmigaWeb.net could serve as a bit of a hub. IIRC, it was set up specifically to cover all Amiga like systems. It could amalgamate recent posts/threads/news from all sites and provide a quick overview along with links. Each forum site would have a directory on the side cross-linking to all the others.

So, what do you people think? Good? Bad? Ok, but unworkable?

Hans

@Menthos

Quote:

I'm focusing more on OpenGL itself rather than GLUT. If someone is willing to have a go at updating GLUT support, they can always access the SVN, and/or contact the Friedens in order to be added as developers.

Hans

@Richi

Quote:

We are working on adding extra functionality and some progress has been made.

Personally, tonight is the first time that I've been able to work on it in a few months.

Hans

@LordArt
Quote:
Out of curiosity, how are things progressing with porting your game to OS4?

Hans

@Paul

Quote:

What exactly is Typemanager supposed to do? I never really understood its purpose as copying fonts to the sys:fonts drawer always worked fine for me.

Hans

@Curty

Is anyone still working on AWeb (not AWeb Lite)? Sputnik is based on Webkit too, so they could have used that code (which is on Sputnik's website).

Hans

Yes, it is a lot better now. It's progressing well. However, I've already hit a few hiccups (documented in the news article comments over on AW.net). And, I've had my first crash too.

Normally I wouldn't post a crashlog here, but I'm rather tired right now, so here's the log:
Crash log for task "OWB"
Generated by GrimReaper 52.3
Crash occured in module OWB at address 0x7F5B6318
Type of crash: DSI (Data Storage Interrupt) exception

Register dump:
GPR (General Purpose Registers):
0: 00000000 68F124A0 00000000 00000000 68D18B5C 00000001 00000030 00000001
8: 8000000F 68D1B494 8000000A 00000133 42004044 6AB6EAF0 6AB66A5C 6AB669D4
16: 0160086C 016007F0 6A8F34FC 00340014 00000001 00000000 000002D0 00000000
24: 68F12C60 6A8F351C 68BA7C98 00000001 68D18B5C 68CDA214 6AB284EC 00000000


FPR (Floating Point Registers, NaN = Not a Number):
0: nan 1.20287e+12 0 960
4: 720 -7.88885e-10 3.8598e-06 0
8: -8.86216e-11 -0.00392924 4.5036e+15 1.013
12: 2.14748e+09 280 0 0
16: 0 0 0 0
20: 0 0 0 0
24: 1e+61 1e-59 0.5 4.5036e+15
28: nan 65536 1.67772e+07 1.20287e+09

FPSCR (Floating Point Status and Control Register): 0x82028000


SPRs (Special Purpose Registers):
Machine State (msr) : 0x0000F030
Condition (cr) : 0x22004042
Instruction Pointer (ip) : 0x7F5B6318
Xtended Exception (xer) : 0x20000000
Count (ctr) : 0x7F5B8C50
Link (lr) : 0x7F5B8C70
DSI Status (dsisr) : 0x40000000
Data Address (dar) : 0x00000000



680x0 emulated registers:
DATA: 00000001 1AA5C5FC 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 6A088720 6BA7E434 00000000 00000000 00000000 00000000 00000000 68F12260
FPU0: 0 0 0 0
FPU4: 0 0 0 0



Symbol info:
Instruction pointer 0x7F5B6318 belongs to module "OWB" (HUNK/Kickstart)

Stack trace:
module OWB at 0x7F5B6318 (section 5 @ 0x2BA2F8)
module OWB at 0x7F5B8C70 (section 5 @ 0x2BCC50)
module OWB at 0x7F5B874C (section 5 @ 0x2BC72C)
module OWB at 0x7F5B6298 (section 5 @ 0x2BA278)
module OWB at 0x7F40B1E0 (section 5 @ 0x10F1C0)
module OWB at 0x7F40B368 (section 5 @ 0x10F348)
module OWB at 0x7F4C6538 (section 5 @ 0x1CA518)
module OWB at 0x7F4C661C (section 5 @ 0x1CA5FC)
module OWB at 0x7F3397D4 (section 5 @ 0x3D7B4)
module OWB at 0x7F33FC70 (section 5 @ 0x43C50)
module OWB at 0x7F33E65C (section 5 @ 0x4263C)
module OWB at 0x7F60D32C (section 5 @ 0x31130C)
module OWB at 0x7F60DC14 (section 5 @ 0x311BF4)
module OWB at 0x7F5F9A94 (section 5 @ 0x2FDA74)
module OWB at 0x7F5F9B40 (section 5 @ 0x2FDB20)
module OWB at 0x7F5FB44C (section 5 @ 0x2FF42C)
module OWB at 0x7F5C4080 (section 5 @ 0x2C8060)
module OWB at 0x7F2FD9B8 (section 5 @ 0x1998)
native kernel module newlib.library.kmod+0x00000de4
native kernel module newlib.library.kmod+0x00002380
native kernel module newlib.library.kmod+0x000028e0
_start()+0x180 (section 1 @ 0x180)
native kernel module kernel+0x00035be0
native kernel module kernel+0x00035c60


PPC disassembly:
7f5b6310: 48000064 b 0x7F5B6374
7f5b6314: 80690020 lwz r3,32(r9)
*7f5b6318: 81230000 lwz r9,0(r3)
7f5b631c: 81290070 lwz r9,112(r9)
7f5b6320: 7d2903a6 mtctr r9

System information:

CPU
Model: Motorola MPC 7445/7455 Apollo V2.1
CPU speed: 933 MHz
FSB speed: 133 MHz
Extensions: performancemonitor altivec

@Amigamancer

Quote:

Extra developers won't come to a platform that they can't buy hardware for. They also won't come to a platform who's future is in the hands of the courts. The court-case does matter.

Hans

@Jurassicc

I'm still looking for that fat lady. I don't see any here. No, no, no, not her; she's not fat, just well rounded.

Hans

@Mikey_C

If the show's not over till the fat lady's sung, what do you do if the show doesn't have any fat ladies?

Hans

@AmiKit

Quote:

Do a search for hollywood on os4depot. Also look up the badger demo and Global Gladiators (on os4 depot). Finally, PEB has released a number of little utilities; you can find them here. There are other examples floating around out there, but I'm not sure where to find them.

I know that Andreas Falkenhahn doesn't release demos of his applications anymore because people cracked them in the past. However, I think that he should provide compiled versions of some Hollywood demos for different platforms that show off its capabilities. It's not like people can crack those to get a copy of Hollywood.

Hans

@Mikey_C

How about waiting until the Allegro port is finally released? There's supposed to be a whole series of games coming. Plenty of stuff to keep you entertained.

I'd also encourage anyone who's got OS4 but isn't a developer, to try learning to code. Writing software isn't for everyone, but you could at least try. To make it easy, buy Hollywood and Hollywood Designer and try using that to create something interactive. The stuff you make initially might suck, but will improve the more you work at it.

Hans

@evilrich

Thanks for checking. I guess that we'll need to pass this on to the Radeon driver developers. Hopefully they'll read this.

Hans

@evilrich

Quote:

BlasterBastards has the flickering problem, but it's closed source.

There are a few demos with the WaitTOF() workaround on os4depot; namely Dr Fungi, yellowrose, and Dr. Fungi goes to Africa.

NOTE: You'll need to comment out IGraphics->WaitTOF(); in the source of those demos to get the flickering.

The flickering happens when Interrupt=yes is set in the monitor tooltypes.

Hans

@evilrich

Quote:

I had a quick look at the SDL source code and saw that there was synchronization code in there; it's just not working the way that it should, at least with MiniGL screens.

Quote:

Thanks. Others reported the same problem.

Hans