Pretty weird behavior this one. When i try to run a game using kronos, it works around 1/3 at the time. Most of the times neither RetroArch or the game loads. Other times the game loads. Without changing any options whatsoever.
Whatâs the point of this topic ? Are you complaining about a core in alpha phase having bugs while not giving any information on the OS neither the commit ?
Wasnât aware itâs in alpha phase.
You are right about the OS though, iâm using both Win7 and 10 and the latest Nightly.
I am guessing there been no Info about Kronoâs has come out.
I thought it was early in Development so I was giving it time until we hear something from Libetero or Kronos Core Maker.
Excited for its Potential
Exactly, there was no announcements about this core, it is only mentioned on this forum and it is said it is WIP.
Also, the buildbot is behaving weirdly with this core (it seems to be randomly building old commitsâŚ).
On a sidenote, i finished fixing the GL renderer a few minutes ago. However i only tried the core on linux, iâm pretty sure there are issues on windows, and iâm also pretty sure you shouldnât trust the buildbot atm for this specific core, try building it manually (there are tutorial about this in the libretro documentation)
2 Likes
It was announced on the Youtube channel, thatâs actually why I came here today. I never would have guessed this was alpha based on what I saw. Glad to know itâs Alpha though, tempers my expectations a bit.
Well, with the announcement, itâs now past alpha. There is still a nasty bug with the core crashing if you switch in/out of fullscreen though, but everything else should be ok. The compatibility should be pretty good too. Now weâll try adding things like tesselation and the likes.
1 Like
Doesnât look like it has CHD support which means I canât use any of my games.
It can always be added, but that is the risk you take when you invest in a specialty format.
1 Like
To be honest, with kronos having real âzipped isosâ support (finally an emulator where i can use redump releases directly !), i have absolutely 0 interest in implementing this myself, so letâs hope for you that someone else will implement this.
2 Likes
True - and I was so focused on cramming my entire build (game library, frontend, control software, & emulators) on a 4TB drive that I didnât see the forrest for the trees.
The real question though becomes âIs Kronos outperforming Beetle Saturn?â I donât ever upscale or anything, but if it has a better compatibility or something that might tempt me to look into re-converting them back to bin/cue.
Speedwise, it is outperforming beetle-saturn : i tried downclocking my i7 2600k to 2Ghz, kronos was still running Virtua Fighter 2 at ~53 fps (with auto-frameskip disabled, so perhaps full speed if enabled ?) while performances in beetle-saturn were crushed (~30fps).
About compatibility, i donât know, afaik Kronos worked for ~80% of the tested games (600+ games were tested), and i donât know of any compatibility list for beetle-saturn, what i know though is that i didnât manage to load an european iso in beetle saturn yet.
With resolution upscaling and tesselation it also looks better than beetle-saturn.
Also, i love the fact it can read zipped cue+bin+wav directly without any issue, converting or unzipping is annoyingâŚ
Well, the only downside i can see with kronos atm is that it requires a compatible gpu (OpenGL 3.3+, or 4.2+ if you want gpu tesselation) while beetle-saturn donât care about that.
2 Likes
Even if you arenât interested in upscaling (and let me tell you that many 3D games look FANTASTIC in high resolution), Kronos is indeed quite a bit faster. In terms of input lag (which is one of the weakest points of Saturn emulation in general), they are equal I reckon. 4-5 frames. Regarding compatibility they are quite close at the moment (at least when it comes to the games that I have tried and usually play). Sound I give the edge to Beetle, Yabause and its forks have always made some games sound⌠unnnatural (although they have improved a lot in that regard in recent times).
Saturn is the only system I keep two playlists for. Both cores complement each other well. I believe Beetle is more accurate in a âMAME wayâ (i.e. everything is software emulated) and Kronos is âhackierâ (HW acceleration, upscaling etc). If itâs speed you are after though, Kronos is the way to go right now.
1 Like
Ooph that hurts my heart to hear lol I was hoping you were gonna say itâs not worth the change as of yet hahaha. Iâll have to re-evaluate my formats I guess. Thanks for the info guys.
Currently, I had some issue with the new Kronos 1.5.0 with the Kronos cached Interpreter. It performs the same as the actual interpreter. Only tested on the standalone. They had the fixes for the FPS cap and the polygon pop in after it. Not sure if the speed issue exist on the libretro one.
How did you measure this ?
I just look at the fps and also, the 1.5.0 has problems with the fps cap, so it can go faster than it should. I tested Daytona. It hovers under 60fps on both interpreter and Kronos interpreter. On 1.4.5, it is full speed and doesnât uncap the FPS. I noticed this when I was testing out the games.
Ok, so you donât really know, you are just assuming the cached interpreter is not working because it is not performing a miracle with your performance issue, while the bottleneck could come from somewhere unrelated to the interpreter. Afaik, the interpreters barely changed between 1.4.5 and 1.5.0, the part that changed the most is the renderer.
Whatâs your setup ? Especially whatâs your gpu ?
Intel GPU support is on the way for a future in this new core?
whats the minimum gpu i can run this on?
@BarbuDreadMon well according to wiki , https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units#Third_generation, i should have D3D 11.1, Ogl 4.2, gles 3.0, vulkan 1.0
0:1(10): error: GLSL ES 3.10 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, and 3.00 ES
[1] 4800 abort (core dumped) retroarch
â ~ glxinfo | grep -i opengl
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Desktop
OpenGL core profile version string: 4.2 (Core Profile) Mesa 18.2.4
OpenGL core profile shading language version string: 4.20
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.2.4
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions: