@Spectre660

Thank you for your explanation. I really appreciate. But even if that clarifies some things ... that should be simple by default.

We have to admit users are confused and that harms our small market and companies that aim to sell more and make users satisfied.

Things have to be simple. I insist on this point because there are some actions to take about that to improve communication (our topic here).

@Spectre660

Quote:

I learned reading your link that "Enhancer Software version 1.x required". What I missed reading its description in AMIStore. And with which variant(s)?

Anyway, another thing that's not logical to me is "Everyone that orders this package will receive a licence for the forthcoming Enhancer Software 2 release". The graphics drivers and libraries can be acquired with the Enhancer Software Graphics Upgrade, that can be seen as a subset of the Enhancer Pack ... that will allow a future update of the pack in which it is contained.

I understood the difference between the content of the 3 flavours of the Enhancer Packs. I just think there are too many variants. And the "Core" version in addition to that!

And about the terminology, I never know if the Special pack is better or cheaper than the Standard pack, if I don't read their description.

My comments and suggestions were not restricted to these Enhancer Packs.

Note: OMG! Your answer made me looking again at the Enhancer Packs content and I just understand that "Warp3DN_SI.library" is Warp3D Nova! My first idea was to buy Warp3D for Radeon SI and thought I will get it with the Enhancer pack! That's not new but reusing the term Warp3D brought confusion.

@Capehill

Thanks for the reminder about svn. Yesterday, I checked locally, I'm pretty sure I installed this new version some time ago ... but it seems that was not on the X1000 ...

About sgit, it should be capable, as I cloned ScummVM with it successfully.

@Raziel

I also tried the mgl/context.h trick. That compiles but crashes starting ScummVM, certainly due to missing hardware support in MiniGL (I switched to a RadeonSI board and don't have Warp3D_SI drivers yet).
I remember months ago I tried to play with namespaces and that was not satisfying. I don't remember well problems I faced at that time but that implied to modify system and MiniGL includes if I remember well.

With your last release of ResidualVM (thanks for that), I get an error ("OpenGLGraphicsManager::endGFXTransaction: Could not load any graphics mode!") but that does not crash.

Note that I compiled ScummVM with SDL1.2 ... I have to install SDL2.0 libs and includes in my SDK.

I wanted to compile the latest version of MiniGL with the removed Intution include but I got an error about the SVN client being too old.

@amigakit

I have suggestions to improve communication making it simpler. Today I tried again to purchase software from the AMIStore app. First I tried to pay with credit card using Odyssey, what failed confirming payment. Then I tried with Netsurf (that was in the choices after I clicked on the checkout button in AMIStore) but it was said this browser was not recommended. I also tried with Paypal but that failed to send me a code on the phone. Maybe our browsers are too old but in this case .. how people use AMIStore?

Seeing that AMIStore opened a page of the amisphere.com website, I went to it, this time using Firefox on Linux. Once logged in, I only have a single page (download) but no shopping bag or products (except Enhancer Software Core that is the fourth flavour).

I go to amistore.net and found "Recent updates on AMIStore" with:
1/ broken links
2/ a product name "Enhancer Software Plus V2 (OS4) (2.0B36)" ... that I did not find in the AMIStore app.

On amisphere.com I didn't find any contact info. And while writing this post and trying again many things, I finally found a contact form on amistore.net in "Account/Contact us".

I think all that is too complicated. Differences between flavours of Enhancer Software should be clearer. For example, within AMIStore, it is difficult to compare Standard and Plus editions. In the Standard edition, there are RadeonHD drivers V1 ... What is the difference with V2? Is it still necessary to provide V1? There is also V3 mentioned in "Enhancer Software Graphics Upgrade". Does it only contain RadeonHD drivers? What do they bring in addition to extending the memory limit above 256 MB?

@Raziel

Quote:

Sanitizers are fantastic tools! I use them as soon as I can (they made me able to send patches to ResidualVM codebase).

Unfortunately, on PPC, even on Linux, their support is not working AFAIK. The libasan is found but that crashes at execution.

I don't remember if I tried with clang (maybe I had other problems to get it working correctly, even without sanitizer options).

I should test again and provide a status.

Edit: Right now, I've just tested on Ubuntu 16.04 PPC with gcc 5.4 and got a valid error detected and reported by the asan sanitizer.

@BobSacomano Ok, I understand better. Thanks.

About Amiga emulation, that should perform better on Sam460. I see there were already some discussions about what you face. One said a monitor mode at 150 Hz ... and there is another source that seems to give more information:
https://www.amigans.net/modules/xforum/viewtopic.php?post_id=88398

It could be a matter of sam460 config in E-UAE and wrong timebase management ...

I never had stability problems with my MicroAOne. However, the 32 MB graphics RAM made me using in in 16-bit mode. And IDE transfers were very slow.

The Sam440 has no L2 cache and its frequency is lower but I always found responsive even with this embedded-class processor. I used the Flex version, not the EP one.

Sam460 has better performances than these venerable machines.

@BobSacomano The CPU is not the single part of a machine. Do you have a use case in mind? Or was it just for a global feedback (feeling)?

@Raziel

Linux would be useful in your case to check with a maximum of memory, 16 GB if I remember well. But I understand you don't want to install it.

I wonder why you bought 16 GB to only run AmigaOS

I will check with 2 GB in each slot.

@Raziel

You have certainly read Cyborg's answer (thanks Michael for having copied questions in the other forum).

I don't know much about problems of KVM switches on X1000 (except I had a bad try).

But about the problem of memory:

1. There is a known problem (crash) at the amigaboot level with more than 4 GB installed. I met it with 2x1GB installed first, and the after having added 2x2GB. Impossible to boot AmigaOS.
How much RAM do you have?
If this is the same bug, it requires a fix in amigaboot.

2. I see what Cyborg means but I don't fully agree. As a bootloader initializes the memory controller and calibrates depending on how memory sockets are populated and by what, a bug may happen there.
We all agree that AmigaOS should manage areas provided with more than 4 GB even if it uses 2 GB.

@xenic Existing programs that use floating points will be slower, from not visible to really slower, as they will require some emulation work by the OS.

With GCC 8, the support of SPE has been declared deprecated but is it possible to enable it?

Anyway, the use of SPE instructions should be restricted to the most essential and reduced part (and with much care).

@salass00

Oops, of course, you're right. I focused on the method to return and missed this call to printf.
Thanks!

The given code works but is not exactly right.
In the asm_func code, the function code should be:



In kas1e's example, the call to the exit() function has nothing to do there. I bet the other call to exit() (in the main C function) is never called.

@Spectre660

Quote:

Oops! I'm so sorry ... I really did not remember. So I did not keep my promise ... I was too far too long ... but after an house, my third child and several job changes, I start again to have some free time

@kas1e

Quote:

Hieronymus is not as advanced as I would like but don't consider it dead yet

I have unreleased improvements that I would have to publish in a new version, to make it working in an alternative mode without machine restriction. And other things.
I was not aware about problems with Sam460.

@kas1e Great! Thank you for that. And I am sorry for not having answered to you and sent the diff. So you did it. I was not sure at all they will accept the patch, as any systems emulate the alignment exception on float accesses.

A comment above the structures could have been added to explain the reason for padding but that good enough.

I hope this engine will allow to provide new software.

@kas1e

Thank you for the links on models. I've sent you a modified loader by email, that could fix alignment problems in an easier way, padding the beginning of structures (still packed) in order to get the float fields aligned on 4 bytes. I dynamically allocate structures and copy the data to the address of the field Flags (just after the 3-byte padding).

I hope that will work!

@kas1e

I will be busy in the coming days but on the week-end, I will attend the Alchimie show here in France so I will be 2 days programming on Amiga with my friends (hey thellier!)

That could be nice to try to make it working there.

Could you provide a ms3d model? All files I find are corrupted archives or they failed to be extracted ...

@kas1e

Ok, you're right about the management of this kind of exception by Linux.

About speed: no difference, that's a matter of few instructions at load time.

What I proposer could certainly be cleaner but how you can avoid a copy in a structure that add an abstraction level, as the initial structure is badly aligned and playing with fields and padding won't give the expected result.

I will have to look at your example as I'm not so familiar with C++ and so I'm not sure to understand what you want to do there.

Glad to see that allowed you to go to the next steps ...

As you said, you will have to fix the part with MS3DTriangle, MS3DJoint, ...

Do you know if a working Linux PPC port exists?