@Daedalus

If you use aos4 for 68k, imho better use winuae already (imho of course). From other side, i personally have no problems if there will be still Petunia, but if its stop aos4 from growing up (on API level), then i am for sure up to removing 68k completely and without any cry. Basically, we not have any good solution for 68k support. We have petunia in os4, but not have chipset support. We have EUAE , but not have JIT inside. We already in situation when we not have normal support of classic stuff, so why need to bother about it, just remove it and spend time on making MP/SMP/good 3D.

But i think it's already on that level, when aos4 developers do not have any priority related to 68k support. I think Rigo can say more about :)

@afxgroup

I also have problem with Giddy and also think about problems with MiniGL. Bug looks like this: for all enemys animation it show white cube and nothing more. I.e. its just not display correctly loaded textures. Its not the same bug for you ?

@Minuous
Imho, djrikki ask about normal amiga sites :) Not having modern features not that bad, but design then must be good. That all smeels a bit too retro and rare.

@BiLLie
Quote:
Now i understand why DU looks not eye candy :) But prepare that users today will choice eye candy + functionality. Not only functionality , or only eye candy. One without other today will give enjoyement only for zx-spectrum fans :)

@djrikki
In general, amigans, amigaworld and utilitybase are up2date and can be called "sites". Even if amigaworld.net today its somethinkg where trolls make their posts, and ppls talk too much about phylosophy of boing :) The other from my point of view "real amiga related site" its amiboing.de. Not so informative maybe, and only about games which do owners of site, but, its very good designed, and show how everything must be done (Minuous, check it too :) )

@afxgroup
What was problems with crashes btw (can you explain a bit techincal details). And maybe put somethere link for tests ?:)

@DAX
I think that even with current realisation of Warp3d, on x1000 it will works fine. Just because of faster memory , faster bus, faster CPU and alt. Even on my peg2 with 1ghz its cant be called as slow (but still, not reactive fast of course).

When i talk with Kiero (author of morphos tinigl), he say that even morphos a bit slower in 3d in compare with the same (almost) hardware but with win32. Not because of drivers, but also because of faster hardware itself (not in terms CPU raw power only, but about all those memory-transfers and alt). So, i expect that all will be ok (maybe even with new Sam). But still, we will loose 50% of speed while warp3d beetwen.

@ALL

New version in os4depot query. Changes since last release:

-- Fixed support for floating pointing textures (such as RGBA32F, etc) for our MiniGL, because MiniGL do not works with FP textures(one more limitation example for all who say that new MESA and 3d are not necessary). so adding conversion/cheking. If no GL_ARB_texture_float present, then convert them to unsigned char. It also solve the problem with HDR images (.hdr and .rgbe formats) at all (before it was buggy on aos4).

-- Give message to the user when a filter doesn't support a certain color mode (before it simply did nothing without any indication why)

-- The crop operation now says in a warning dialog that a selection area is required for it to work.

-- Began internal code refactoring of dynamic operation parameters. When done, they will be convertible from/to everything, like XML, GUI dialogs, C-structs, plugins, etc...

-- And the most interesting: Plugins support ! For now plugins diveded on 2 types: filter plugins and image_format plugins. Filter plugins its for making more new filters, and format plugins its for expand lodepaint buy new file formats. With that release there is 1 filter plugin and 3 image_format plugins. While filter plugin do nothing so usefull (its just example of "sine" filter), image_format plugins are interesting :

-- LibJpeg plugin: by default LodePaint have internally reading/saving only classic jpeg, and not progressive ones. When you will put libjpeg plugin to plugins directory, lodepaint will automatically swith to new plugin, and you can works with any kind of jpegs (include progressive).

--DNG plugin: for working with DNG images (format done by Adobe, and for making that plugin uses SDK from Adobe). Prepare that DNG images sometime very heavy (10-20-50 megabyte of size), so, for slow amigas with slow cpu and small amount of graphics memory it will be a pain and problematic (but still, can be usable on modern hardware).

-- OpenEXR plugin: for working with high dynamic-range (HDR) image file format developed by Industrial Light & Magic.

For using the plugins, just put from "plugins_unused" direcotory these plugins which necessary for you to the "plugins" directory. In general just copy them all.

I also make LodePaint for now as dinamic binary (to make it works normally with plugins), so, very possible that some errors can happenes. Feel free to post here any bugs/problems which you have with.

@BiLLie

Imho, Digital Universe totally unmodern. Its like you use some good programm, but done in the 1980 year. More visuals, more animation, more dinamic and graphics are need it for (imho of course).

@afxgroup

Why i ask about, because looks like when main binary are dinamic, GR cant say you exactly where crash is happenes, and refer just to newlib.kmod only. But when its static - you can see where is crash in programm happenes. But for see that, you need main static binary and your shared plugin , which, you cant link with any .a looks like (so, pluging then make no sense in that terms, just becasue plugins usually done for all those 3d party lib.a which you add to your plugin). But when all is -use-dynld, then all is ok (except that you cant normally detect where is crashes happenes)

For now i just create a plugin without any references to any .a , and then trying to catch error, but, in generall, its bad that i cant see where is crash happenes when main binary is dinamic (or can ? )

I also try to use GDB, but it crashes like hell, and just cant load or attach from GR that main dinamic binary at all.

Btw, can i somehow mix .a files (which was not compiled with the -fPIC option) for my .so plugin ?

For example i have libjpeg_plugin.so, which i compile like:
Quote:

So i use libjpeg.a, which was compiled without -fPIC option, do i need to build my own copy of jpeg.a , with -fPIC option ?

@xeron
Btw, did you read that with the latest PFTP mouse scroll by wheel does not works for now (not only for me, but if i remember right for 2 more users too) ? (can try to found topic about)

@Swoop

I (for example) not use any 68k program on my os4. Only 1 time in half of year, running some games/demos over euae for 30 minuts , just to see that it works. All the stuff which i really use every day - os4 native (and i think i am not alone with it for now).

@Daniel

You are right. But if i remember right, that question (about prefs and alt) was discussed some times, but still, we have that little mess.

@TSK
Quote:
Imho it must be removed just because its old and must die at all with all those rare freaks and retro fans :)) But if say seriously, having 68k support on kernel level stop aos4 from growing up. I see no problem to just put all that 68k support code to "box", just like win32 with ms-dos support, or macos_some_version with older macos.

That will give for aos4 coders more freedom, when they will make aos4 more mature in todays standards. Imho making memory protection, resource managment and alt will not possible with having in mind 68k api support.

Making it "in box" will solve many problems, and more of it: euae have chipsets support , while petunia are just 68k support, what for new blood/users (which we need) have no sense.

@djrikki

OWB
Mplayer
Dopus4
Filer
WookieChat
PFTP
Tunenet

That all what i use mostly. There is also some cool apps which i use from time to time, like DiskImageDevice (mounting of isos/etc) and inbuild Sgrab utility from aos4 distrib (for making screenshots :) ).

And of course shell + kcon (kcon it's replacement of default con:, because by default aos4 have ugly and primitive shell still) and notepad :)

@Chris
And now more funny. I have for all plugins, such crashlog when close main programm:

Quote:

I add stack cookie to each plugin, but still, error the same, and happenes when i close main programm. What can cause such problem ? (and error, always the same, for any plugin, on always the same addresses).

How can i trace where is problem ?

For one plugin that crash happenes when i only run/close main programm with loading plugin. Other plugin crashes when i load programm, open a file, then exit, and then have such crash.

@Chris
I cheked my plugins, and one of them:
Quote:

other one:
Quote:

and another one:
Quote:

So, its everythere.. And when i compile main programm as static, always have such error.

@Swisso

:)) and cup, сap and of course boing-tatu on soft place :)

I am for video subsystem / 3d changes/speedup. That is the most important part of OS which can bring for us new blood, and will give us more enjoenable and modern software (and with bigger user base, we will have more software).

Then removing 68k support from core at all, add JIT from petunia to EUAE and make EUAE as default for running any 68k programm.

Then memory protection / resource managment (for killing all the tasks with all those windowses/resoruce opened by app) and alt :)

@varmfskii
Porting of apps already not so hard. In general all problems with porting usually come to bad source code initially. All programms which done in good way, need only few changes (like add stack cookie, change linking libs and add PROGDIR: except all that linux stuff like /usr/bin and alt).

@djrikki

Of course :) Because when you have 1ghz of cpu maximum, usage of any screen-recording programm make no sense (will slowing down everything a lot).

But for sure, quality can be better :) Need to buy someday some kind of HW recorder.

@djrikki

Are you sure that you want TW , but not OWB for example ? TW are very buggy must to say for now, so i need to reboot everytime after i visit more or less heavy sites :) (OWB in that terms very stable, and can render all that FaceBooks, Youtube and alt).

Anyway, if you do not have aos4 by hands, but want to see some more stuff, check some of my videos on youtube here.

That one imho most interesting one (aos4.1 update 1, with all that Youtube in action and such).

(Will make some other-different shots later)