Posts: 19
Threads: 5
Joined: Nov 2012
Reputation:
0
I made this thread, probably in the wrong section too, anyway. So I updated to 1.2.1 just now but when going to plugin/bio selector I notice some red ominous text in the console that looks, well ominous. Nothings broke as far as I can tell but I'd still like to fix this if possible, I don't remember this in previous builds but 1.2.0 is now overwritten. Oh and you can ignore this if this is perfectly normal and everyone gets the same message.
Attached Files
Thumbnail(s)
Posts: 574
Threads: 5
Joined: Jan 2012
Reputation:
42
Location: Ireland
02-04-2014, 01:54 AM
(This post was last modified: 02-04-2014, 01:54 AM by Asmodean .)
It's only because you're system doesn't support avx2. Removing that avx2 gsdx plugin will remove the messages.
Posts: 19
Threads: 5
Joined: Nov 2012
Reputation:
0
Really? I though Ivy Bridge processor supported AVX.
My spec's.[/align]
Attached Files
Thumbnail(s)
Posts: 8.013
Threads: 133
Joined: Nov 2009
Reputation:
96
Location: Delft, The Netherlands
AVX 1.0 yes, but not 2.0 which is for Haswell cpu's
Posts: 19
Threads: 5
Joined: Nov 2012
Reputation:
0
Welp, you guys are right, and deleting the AVX2 plugin removes this error, thanks!
Posts: 12.837
Threads: 48
Joined: Oct 2013
Reputation:
252
02-04-2014, 02:16 AM
(This post was last modified: 02-04-2014, 02:20 AM by Nobbs66 .)
It's only supported by Haswell cpu's.
Damn, already beaten to the punch.
Posts: 4.504
Threads: 14
Joined: Jul 2009
Reputation:
89
02-04-2014, 06:50 AM
(This post was last modified: 02-04-2014, 06:52 AM by nosisab Ken Keleh .)
Far better is not having any error/warning message and getting a catastrophic failure without a clue
If was not for the error message you'd be mistakenly believing that processor supports the extension.
Edit: I think I understand what you mean, it's actually a healthy concern, just sometimes warning messages are unavoidable.
Imagination is where we are truly real