[UserReview] Vampire V2-128 received and it's just pure p0rn.

[kolla]

But now que comments about missing MMU in 1...2........

It's not missing, please pay attention.

[Nickman]

It's not missing, please pay attention.

Sorry can't keep up with the trolls.
Now it's more like.. But still no 68040 compatible mmu..... Right? Or are we past that to?

[Niding]

A bit more painful fpswise, but its working!

AmiQuake2 1.06 RTG on GOLD2.7 WIP

https://www.youtube.com/watch?v=oCvydjZVqO4

[kolla]

Sorry can't keep up with the trolls.

You should keep up with what the lead developer of the Apollo Core is writing and saying, it is more than a year ago he explained that the Apollo has its own MMU, and why it is what it is. And noone has any problem with that either, but there is a problem if it remains closed, which appears to be the case.

Now it's more like.. But still no 68040 compatible mmu..... Right? Or are we past that to?

Being compatible with 68040 MMU doesn't make much sense, since noone is planning to use the Apollo Core along with a 68040. By not being compatible with existing software that uses 68k MMU, the apollo core is missing out on many opportunities, but considering what it is used for (to host Amiga OS on alien hardware), that is understandable.

[kolla]

Btw - "femu 0.11-WIP is Apollo core optimized version (includes HW 040 and 060 FPU)" - what does that mean? HW as in hardware? So, the Apollo Core for V2 now has a 040/060 level FPU (something that was cancelled earlier), and all FEMU 0.11-WIP does is trapping the remaining instructions, very much what the 68040/060 libraries do? If so, maybe it should be implemented as a 68080.library?

[Niding]

@Nickman

You know, we might be fussed at time that some people are being overly negative about Vampire, but it doesnt help poking people in the eye at every oppurtunity.

I might not agree with all of kollas comments/view of roadmap, but he does have some good questions overall.

@kolla

grond made a comment on EAB;

"This is the relevant part: "includes HW 040 and 060 FPU".

But the HW FPU parts are still throtled for testing. "

http://eab.abime.net/showpost.php?p=1193992&postcount=167

[Niding]

Posted by Gunnar on Apollo forum;

http://www.apollo-core.com/knowledge.php?b=1¬e=10848

Hello Coders,

GOLD 2.7 will come with AMMX2 instruction set.

Please find here a preview of the AMMX Quickreference chart:
CLICK HERE

http://www.apollo-core.com/AMMXQuickRef.pdf

[Niding]

Amiga 600 vampire 2 Gold 2.7 testing: Elude - Soliloquy

Camrecording by Mr-Z, so not the most flawless demostration, but shows the performance of the 2.7.

https://youtu.be/xEtd8td2a7o

Amiga 600 Vampire 2 X11 core Gold 2.7 Hires Quake 640X400

https://www.youtube.com/watch?v=GpqSUCm1Fcg

Amiga 600 vampire 2 Gold 2.7 testing: Elude-We Come In Peace

https://www.youtube.com/watch?v=KHFgEo4Ir3Q

[ddniUK]

Thanks for the videos.
What is the framerate in Quake? Can you run a timedemo please.

[Niding]

I dont have access to Gold 2.7, so ask Manuel these things via youtube.

Updated  play with X12 core:

X12 core

https://youtu.be/w2S4suHf-l8

[Niding]

http://www.apollo-core.com/knowledge.php?b=4¬e=11558

Last night we started to play around with some texture mapping code.
 
Here is a very early result:
http://www.apollo-core.com/gfx/V3_demo34.mp4
 
The screen is rendered in 640 pixel width.
The texture routine uses bilinear texture filtering.
https://en.wikipedia.org/wiki/Bilinear_filtering
 
more to come

[Louis Dias]

http://www.apollo-core.com/knowledge.php?b=4¬e=11558

Goodness!  What's next - mip mapping?  

[kolla]

Well, that's far from smooth...

[ferrellsl]

Well, that's far from smooth...

And the texture demo won't even run on a stock Amiga, so what's your point?  Was your post simply to reconfirm that you're a Vampire troll, or reconfirming that you're trolling the Vampire?

[kolla]

a stock Amiga

Always comparing with "a stock Amiga", I am sure you could aim higher

so what's your point?  Was your post simply to reconfirm that you're a Vampire troll, or reconfirming that you're trolling the Vampire?

Not at all. As I have repeated for you over and over again - is it not the hardware I have issues with, not the Vampire.

My point is that it was far from smooth, and I am sure the Apollo Core will now be trimmed and the routines hand optimised to fit exactly this use case so that it will be smooth.

[guest11527]

My point is that it was far from smooth, and I am sure the Apollo Core will now be trimmed and the routines hand optimised to fit exactly this use case so that it will be smooth.

Not quite clear to me what your point is. Of course, if you optimize to a particular target, you get better results. The instruction set has - possibly - been optimized for this particular use case, and the assembly has been particular been optimized to take maximum advantage of the extended instruction set. That seems to be completely legit to me, no problem.

The question would be how generic the instructions are so they can be carried over to another use case. I cannot answer that, but as far as I know, the instruction set is documented, so you can check.

Or, to put it in a different way, all the extended instruction sets of the x86 where obtained in exactly this way, namely by looking at particular use cases (such as 3D rendering) and providing short cuts for exactly such cases. Looks all fine to me.