Thanks, I see, I was wondering what code/command best to use for SSE4.2 ?, one I sed just get errors
Unless they is an update to update it's list of instructions ?
Am on AMD my max is FMA4 , i was trying to push it to it's limit
My list: *snip screenshot*
How does "this is my PC" contribute to this discussion at all?
Pm you, maybe, but some builds are made for intel are amd, try windows / amd -
https://builds.citra-emu.org/citra/nightly/
What? amd64 is the name for a 64 bit flavour of the x86 architecture (commonly referred to as x64 or x86-64). It was designed by amd, hence the name. Intel implements the same architecture.
After so many month tinkering with the codebase you should have known.. it's only one google-query away.
I think gdmk most probably get the resource from
@wwylele ， by the way the newest 31-8 build fix the the frozen/hanging problem in X/Y whenever we getting item as well as starters?anyone please?
Again: What? The source code is public. Anyone could create an unofficial version like this if they are a half competent coder (like gdmk seems to be). Also wwylele rather strongly believes in this Open-Source stuff, he's been actively contributing to our GPL codebase. I'd be very surprised if he even had enough time to work on any secret project with gdmk with personal life, the official version and useless discussions with drwhojan et. al.
44 posts for nearly a week?
Meh.
Thank you, I also wonder how this is possible... oh, that's why:
HOW DID YOU MANAGE TO BOOT CITRA ON 32-BIT?! I'm afraid that a lot of the 32-bit users will beg for more on Citra's Facebook Page and Citra Discuss.
Maybe you had 64-bit once and convert it to 32-bit.
This was answered before.. so why bother asking again?
//Edit: No, this didn't upset me. What bothers me more, is that you replied with a useless post *again*. If you want to say sorry do so via PM. But frankly, being objective is standard forum-etiquette / discussions should not be emotional (= I do not need a PM for this
)
he said friend of his built it for 32, which i think is impossible to do.
And while I appreciate this reply to the previous post: 32-Bit *does* work.
However, you won't have a shader JIT and you probably won't benefit from any CPU optimizations.
This means very poor performance on already outdated CPUs. This means it's a lot of overhead to maintain the build even if they don't serve any use (they will be too slow + very few users). By the time faster is more functional very few people will still use 32-Bit and more importantly: it would mean twice the amount of work for a JIT.
Also most old PCs which still sport a 32-Bit CPU don't have GL 3.3 either (and handling a software implementation would also be too heavy for these CPUs)
So the FAQ states that we do not support 32-Bit officially. This means it might be broken from time-to-time and it also means you'll have to compile it yourself.
Given that the emulator was even shown to work on ARM before, it's not far fetched to assume the codebase is rather portable (minus the JITs) and we won't break 32-bit often.
But it's literally a handful of clicks away if you know how to set up your compiler (which I won't help with because.. no official support for 32-Bit)
I have a 32bit and I run Citra just fine.
That was kind of a troll-move to begin with. How is performance for you on 32-Bit?
PM to us your 32 bit citra for testing,your photo does not proof anything,unless you show in youtube or video , btw your 32 bit build was compiled using latest commit?
(See.. troll-move)
Also: if you have a personal question, why don't you PM them directly and ask for the build? If they get too many PMs they can just share the build publicly (but they'll have to comply with the GPL then)
@
BigOnYa:
