@Capehill

Quote:

Ohh YESSS :)

@AmigaOldskooler

Quote:

I have this Game here in my porting dir and it seems* to work



* It's a version from ­2010 and i haven't looked at it for about 10 years. So gimmi some time to test. At the moment i cannot say what was wrong 10 years ago... I'll upload soon a beta to a file-service or if everything seems to be ok a version directly to OS4Depot.

@Capehill

Quote:

I never experienced this. But i also had initially some problems which i could solve. I tested it successfully with Xbox One S, PS3 and a pair of Nintendo Switch Joycons. -> All Wireless <- You could try the following steps:

- When i write "delete" you (or someone else) should know where to obtain the files again or better backup them ;)

- Unplug ALL Game Devices
- Reboot

- Delete the following files from SYS:Libs/AmigaInput
- PCI_SoundCardHornet.driver
- PCI_Soundcard.driver
- PCI_sblive.pci
- PCI_GamePortHornet.driver
- PCI_GamePort.driver

- Delete all Files within SYS:Prefs/Env-Archive/Sys/AmigaInput/
- Reboot

- Plug the MAGIC-NS Stick into an USB Port (Don't connect your Gamepad via USB Cable - Bluetooth works perfect!)
- The MAGIC-NS Stick has a small Button, select "DINPUT" Mode (should be indicated by a blinking blue LED)
- When the MAGIC-NS LED blinks blue it is time to switch your Gamepad on

- IMPORTANT NOTE HERE - When you switch your wireless Gamepad on - ENSURE BOTH ANALOG STICKS ARE IN NORMAL POSITION

- Click the Button on the MAGIC-NS stick and the "Connect"-Button of your PS4 Pad
- If you successfully paired your MAGIC-NS Stick and Controller, the LED of the MAGIC-NS Stick should stop blinking and light constantly in blue
- Open AmigaInput, select USB, you should see MAGIC-NS whithin "Drivers" Tab
- Select it

- DON'T CALIBRATE YOUR GAMEPAD !!!

- It should work now perfectly
- Test it (only) by moving the sticks and pressing the Buttons
- Save

@jabirulo

Yes, the right stick works flawlessly. In the debug output the left stick is denoted as "AXIS 0 and AXIS 1" and the right one as "AXIS 2 and AXIS 3".

@Capehill, @jabirulo

Both analog Sticks are working using an MAGIC-NS USB Adapter and a Xbox One S Bluetooth Controller.

In AmigaInput the right Stick is show as Z-Axis / Z-Axis rotation:



In Tower 57 the left stick moves the character while the right stick is used for aiming.

2 more

@jabirulo

Thanks, will have a look at them later.

I took care about proper Fullscreen Support. As by the source of the current Version (1.3.1) theres only this in code:



anyway i fixed, rather implemented it, including Tooltype Support. Exclusively for OS4

@jabirulo

The release of such a great Game like Celeste cannot be postponed

Since Controllers are working now i'll have a look at the fullscreen mode and maybe smt else. Will upload a new build soon.

In the meantime i thought about that "gamecontrollerdb.txt" Database stuff. It's a bit annoying if you want to use an 'unregistered' Controller within various SDL2 based Games. The necessity to edit it per Game/GameDirectory could be avoided by moving it to ENV: so having the database globally available for related games using it. Maybe as a fallback and/or option to override the global one, the Game could still look inside current Directory for one.

@jabirulo

Thank you for the code snippet you've pasted into the comments section of Celeste on OS4Depot.

I was wondering why:


was failing even with my Controller already added some time ago to the gamecontrollerdb.txt.

Anyway i executed "testgamecontroller" again and got a slightly different result than the one i've pasted earlier into this thread.



With the newly created mapping the controller works now as expected.

Also for me... it seems close to impossible to get the updated X5000 UBoot Files.

I wrote already multiple E-Mails to AmigaKit (short ones, long ones, always polite) --> Never got any answer!

I read here or in some other Forum it would be best to simply give them a phone call. Did that. Was pleased to write an E-Mail... Called them again...

Can it be that complicated to put those files behind the AmiSphere Login, where i can access already manuals ect?

@aclogic

Yes, as in X5000 Manual written, only 10 Lanes (P5020 and P5040) are used. Do you know why? Any further information about that design?

I cannot help you with ACUBE SYSTEMS ONLINE STORE. Write them an email and give them a couple of days to respond.

I can't see any changes regarding supported RAM size in Uboot 2015.a changelog:

http://www.acube-systems.biz/index.php?page=news&id=134

Only: "removed 2 GB limit for USB sticks" but thats something different.

You did it! Congratulations :)

Probably someone before you re-glued the cooler. On some 460 Boards the cooler simply fall off when moving the case. The glueing pad doesn't look as the ones i've seen from Acube.

Anyway now enjoy your properly cooled Sam460ex and continue tuning it :) (Configure Kicklayout, add a hotkey to enable 460PPC L2 Cache, install latest U-Boot and try out the memory speedup options, ...)

I had this active Cooler called "Red Baron" from "Marcus Computer Germany" on my Sam460ex. Meanwhile i sold the Sam and bought an X5000. So it's already some time ago when i installed it on to the CPU of the Sam460ex. But as far as i remember i performed the following steps to install it.

Don't perform the following steps if you feel uncomfortable with them. If so better ask someone for help. Don't blame me if something goes wrong as I will not take any warranty on the following instructions:

1 - Preparation:

- Bring the Sam460 Mainboard into a position where it is comfortable to do this maintenance work (on a desk)
- It is ok or even good to keep the Mainboard for this Task installed in the case
- Remove the Memory Module and the PCI-e/PCI Cards (This is just a security Step when you remove the passive Cooler)
- When you have the Mainboard in front of you the PCIe/PCI Slots should point to your Body and the external Connectors of the Mainboard (USB, Network) should point to the left
- Do some ESD preparations

2 - Removement of the old passive Cooler:

- Be careful!
- Left Hand Fingers: Place Thumb below CPU/Cooler and forefinger above CPU/Cooler directly on the Sam460 Mainboard - No force here!
- Right Hand Fingers: Grab with the Fingers of your choice the old Cooler and pull it. You maybe need to use some slight force to get it removed. Try to balance this force a bit out with the Left Hand (still on the Mainboard)
- The cooler will flake off jerkily (Because of this i recommended to remove Memory Module and PCIe/PCI Cards)
- Clean the CPU with a lintless cloth and a drip of pure Alcohol added to the cloth

3 - Installation of the "Red Baron":

- As before: You should have the Mainboard in front of you so the PCIe/PCI Slots should point to your Body and the external Connectors of the Mainboard (USB, Network) should point to the left
- "Red Baron" should be installed with its power cable showing into the opposite direction of the PCI Slots so Power cable away and not to the direction of the PCIe/PCI Slots
- Look BEFORE removing the foil from the gluing pad how to properly place the "Red Baron" onto your Mainboard. The cooler should cover the PPC CPU completely and sit straight on it
- Remove the foil from the gluing Pad of the "Red Baron" Cooler
- Place the "Red Baron" Cooler as described two steps earlier on the PPC CPU
- Add some light force on top of the cooler frame, the screws - NOT the propeller
- Connect the power cable from the "Red Baron" Cooler with the power supply

4 - Finalization:
- Reinstall the memory module and your PCI-e/PCI Cards
- Switch the machine on and see if it is booting and the propeller on the "Red Baron" Cooler is rotating

Good luck!

Hi,

you can't enable DMA on OS4 for the onboard SATA2 Port of the Sam460ex. ACube Systems never published a Device Driver with DMA Support for it. Because most of the people tend to use a SiI3114 SATA Controller and prefer to plug someting else into the PCI-Express X1 Slot which is mutually exclusive to that SATA2 Port.

http://www.acube-systems.biz/index.php?page=hardware&pid=5

@samo79

Quote:

In default window i have ­210 FPS
While on smaller screen i reach 830 FPS

Anyway animations doesn't look and interaction doesn't feels like 210 FPS. This affects all Allegro Games. It's a bit better in Fullscreen.

Do you still have an AmigaOS 4.1 Installation NOT Final Edition around to verify this problem exists or not on OS4.1 prior FE. I had a Sam440ep in the past and don't remember this "handbrake" behavior.

@samo79

Quote:

Yes, simply everthing using Allegro Library causes 100% CPU Load, this is the problem we need to get rid of!

@jabirulo

I perfomed the steps as written in README.NOW

Contents of the MAPPING file:

Quote:

However, step "4)Re-run testgamnecontroller"

prints:

Quote:

@Capehill

Quote:

https://www.amigans.net/modules/xforum ... id=116672#forumpost116672

@samo79

Quote:

Paranoid will probably show the same cpu load. Anyway it would be interesting how much FPS you get with default settings. When you have the FPS value for the default settings you can press the 'M' key 4 times on your keyboard to render the game only in a small frame. This FPS value would be interesting as well.

@samo79

Thank you for providing this comparison but as written on OS4Coding:

https://os4coding.net/forum/optimizing ... es-library-threading-code

This is not the problem, it was only an initial assumption.