Closed GoogleCodeExporter closed 8 years ago
Did you put the wrapper(glide3x.dll) in the project64-folder?
Are the pllugin (glide64.dll) & the config-file (glide64.ini) in the
plugins-folder?
Original comment by WC-Preda...@web.de
on 1 May 2011 at 8:43
Yes, I put glide3x.dll in the project 64 folder. I also put glide64.dll and the
glide64.ini file in the plugins folder.
Original comment by nxtand...@gmail.com
on 1 May 2011 at 2:45
I'm using the public release and not a WIP release. Should I use a WIP version
instead? If so, which one?
Original comment by nxtand...@gmail.com
on 1 May 2011 at 2:52
I use this one: http://code.google.com/p/glidehqplusglitch64/downloads/list
Original comment by WC-Preda...@web.de
on 1 May 2011 at 3:10
I can only get old versions to work. The newest one I can use it Glide64
'Napalm' 1.2.
You can find it here:
http://glide64.emuxhaven.net/files/Glide64_Napalm_PR1_2_2.zip
Original comment by nxtand...@gmail.com
on 1 May 2011 at 11:21
Direct-x from june 2010 & vs2008/2010 installed?
Original comment by WC-Preda...@web.de
on 2 May 2011 at 8:04
I had a feeling it was a software issue! I need to install those!
Original comment by nxtand...@gmail.com
on 2 May 2011 at 8:48
You mean Visual C++ 2010 Redistributable Package right?
Original comment by nxtand...@gmail.com
on 2 May 2011 at 8:55
Right
Original comment by WC-Preda...@web.de
on 3 May 2011 at 8:03
I'll install those and see what happens.
Original comment by nxtand...@gmail.com
on 3 May 2011 at 11:59
Well, I installed everything and Glide64 still doesn't work. Are there any
system requirements for this plugin? I'm using a terrible Intel GMA950
intergrated graphics card. I know it's a piece of junk. It works fine for n64
emulation.
Original comment by nxtand...@gmail.com
on 4 May 2011 at 1:25
Lots of people are having this problem and fixing it without any problems. No
matter what I do, glide64 won't work. I am ready to give up. Should I take this
issue to the emuxhaven forums?
Original comment by nxtand...@gmail.com
on 4 May 2011 at 3:28
Yes, this is not a forum for helping people learn how to use this plugin. If
your computer is setup properly, it should be a matter of placing these files
in a couple directories and have it work fine.
Original comment by wespipe...@gmail.com
on 4 May 2011 at 4:49
I'll ask about this issue with glide64 on the emuxhaven forum. Thanks for all
of your help. If it is possible, could someone remove this issue?
Original comment by nxtand...@gmail.com
on 4 May 2011 at 1:51
Original comment by gon...@ngs.ru
on 7 May 2011 at 1:50
I found out the solution to this problem through using something called
depends.exe and I found that after putting both wer.dll and ieshims.dll into
windows/system32 folder, the plugin was able to load on my re-installation of
windows after upgrading my PC.
On a side note: After upgrading my PC, all N64 games have no slowdown except
for the slowdown that was on the real console itself.
Original comment by Yug...@gmail.com
on 24 Jun 2011 at 12:47
I was having this very same problem with my Windows XP SP2 32 bits installation
here. Whenever I visited the settings menu to choose Glide64 WIP from the
graphics plugin tab, Project64 1.6 and 1.7 Beta would show me a message that it
wasn't able to load the Glide64 plugin. The most updated Glide64 version I
would be able to use would be the Napalm 1.22 public release. Fortunately I
recently got through this problem by installing .NET Framework 3.5. It can be
downloaded from here: http://www.microsoft.com/download/en/details.aspx?id=21
I downloaded the bootstraper, ran it and then it downloaded a file of around
71MB. After the installation it prompted me to restart Windows. After that I
could finally see the Glide64 WIP release in the settings menu.
I wish this can help others with a problem alike.
PS: even after the .NET Framework 3.5 was installed I wasn't able to see the
wer.dll and ieshims.dll files in the system32 folder.
PS: before installing .NET Framework 3.5, I installed .NET 2.0 and 3.0, and
also Visual C++ 2010, but the problem would persist.
Original comment by famic...@gmail.com
on 5 Oct 2011 at 12:51
Original issue reported on code.google.com by
nxtand...@gmail.com
on 1 May 2011 at 4:41