[$threadinfo[title]]

[Dominator]

Dear UltraHLE 2064 users,

We are well aware of the problems you may encouter with the first UHLE 2064 release. So many various changes have been added in a rather short period of time that we expect you to help us bust various problems.


If you notice any trouble with the plugins system, feel free to report it in this thread.

Please make sure to read the help file first.
Give us as many details as possible on your hardware/software configuration aswell as the plugins version/configuration.

We are also interested in hearing reports concerning our Xengine plugin when ran on other emulators.

Thanks for your contribution.

- The Staff -

[BTM]

da, my spec bellow, running Mario 64

w/ azimers SPU - crashes all the way
w/o ( internal UltraHLE SPU ) GPU : D7/OpenGL - runs OK but at 5/6 FPS ( ARGH! )

[Dominator]

Internal audio is the most stable and fastest solution in most case.

Concerning, graphics, if the Xengine plugin (UltraHLE gfx) provides slow results, please try out Jabo's d3d 1.4 or any other plugin that runs with your system and let us know.

[Yevun]

After messing with some of the plug ins noticed that you were corret about internal sound. I have gotten very few scratchs/ or cracks between sound effects while the other (mostly the azimers audio plugins) cause the prog to crash. As well as when i try running in openGL. I add the msvcr70.dll file from PJ64 which had cured previous crashing issues. So far games run alot faster and stable then PJ64 but with more flaws then PJ64, noticing the mipmapping texturing techniques seem a off and the clipplane is also buggy. But so far seems VERY VERY promising.:n64:

[ScottJC]

I can only use the internal audio plugins, azimers crash after 5 seconds, and others just sound bad, the internal one works fine, its more than acceptable :happy: well done guys.

[BTM]

- Jabo 1.4 DX6 and 7
- internal uhle SPU

No sound
Sprites problems ?

[BTM]

TR 64 OpenGL 0.7.6
Starts nice, window "configure the ucode" pops up, when going to Options>Configure Graphic Plugin the system locks up

1964 OpenGL v4.5.0
Starts up, goes black, FPS ~30

[BTM]

Unofficial DedalusD3D8 0.08 Rel. 2 - same as 1964

glNintendo64() v0.2.1
error : NV_register_combiners not supported, combiner support disable ...

then goes on and looks like this :

[Dominator]

the clipplane is also buggy

Unfortunately, this is one of the bugs that appeared in the last changes, few hours before release. This was the current (and temporary) price to pay for a wider combiners/ucodes support.

azimers crash after 5 seconds, and others just sound bad

What version of Azi's plugin are you trying? I am using the 0.40 beta version (no options selected) with Glide UHLE gfx.
It works most of the games I tried (Aerogauge, Army MEn air Combat, Super Mario, smash bro, snow board kids).

[Flash]

1) Glide64 - When i press F12, it goes fullscreen but shows only blackness of space with VI X.XX in lower left corner

2) "Internal" Glide plugin - some gfx (i.e. Doom64 text) is screwed up on V3 and V5. fix for old UHLE doesn't work.

[BTM]

Originally posted by Dominator
What version of Azi's plugin are you trying? I am using the 0.40 beta version (no options selected) with Glide UHLE gfx.


I'm using Azi's plugin 0.40 beta and it crashes the emu all the time

[Flash]

Yep. Same thing. Azi's 0.40 beta works ok with 1964 and PJ64 but crashes every time with UHLE2064

[ScottJC]

I'm using Azimer's Audio plugin 0.40 beta 2

[Johann]

With Jabo's D3D 1.5, Mario 64 doesn't have any gfx issue :)

With the new UltraHLE plugins, in OpenGL there are some sprite issues and poligon clipping (in Mario64 some sprites are black). Also, in D3D there are some minor gfx issues :(

[BTM]

[OT] dam mario looks MAD on the screen ;]

[Johann]

Nintendo intro in Mario Kart running with the UltraHLE D3D:

[ScottJC]

hmm, i can't even get jabos direct3d6 1.5 working, just a black screen.

[Eddy]

1) sprites are black in mario 64

2) mouse pointer doesnt go invisible in dx7 (Xengine)

3) Various clipping issues in mario 64

+ speed is real good, sound is perfect with azi .30 (old driver)

[Olger901]

All Jabo's Graphics plugins work
All Jabo's Sound Plugins Don't work
The X engine (Doesn't matter if its OpenGL or D3D) of UltraHLE crashes after a game boots up and gives another error.

[BTM]

Originally posted by Sayargh
hmm, i can't even get jabos direct3d6 1.5 working, just a black screen.

it was said that 1.50 dosn't work with uhle 2064, try 1.40

[fivefeet8]

gives me a "initialize plugin first" message when trying to configure jabos d3d plugins.. 1.4 and 1.5..

[mmcoder]

I have a lot of the previously mentioned problems, but Jabo 1.4 D3D + internal audio (w/ "no sound" also selected) + always using rom browser takes care of most of them.

However, there's one big annoyance left: when I go to full screen I get flashing at the bottom from the status bar. Basically the emu video and the status bar are fighting for visibility for some reason. I've seen this happen in ultrahle 1.0 with glide wrappers also. When I go back to windowed mode, it continues flashing

[Azimer]

Originally posted by Johann
With Jabo's D3D 1.5, Mario 64 doesn't have any gfx issue :)

With the new UltraHLE plugins, in OpenGL there are some sprite issues and poligon clipping (in Mario64 some sprites are black). Also, in D3D there are some minor gfx issues :(

He looks like he's shitting a buick.

[BTM]

Originally posted by fivefeet8
gives me a "initialize plugin first" message when trying to configure jabos d3d plugins.. 1.4 and 1.5..

not plugin but DLL, you can only configure it while the game is running

[BTM]

Originally posted by mmcoder
However, there's one big annoyance left: when I go to full screen I get flashing at the bottom from the status bar. Basically the emu video and the status bar are fighting for visibility for some reason. I've seen this happen in ultrahle 1.0 with glide wrappers also. When I go back to windowed mode, it continues flashing

Sometimes selecting Emulation>Reset helps

[Lear'nos]

As for Jabo's video plugins, copy msvcr70.dll from PJ64 folder to UltraHLE folder (not UltraHLE/plugins).

Then you'll be able to use them.

[Eddy]

i have the flashing statusbar problem too in fullscreen

[milen]

1. Glide64 didn't work FPS counter is active there is sound but not graphics.
2. Internal Glide Plugin show not right alligned textures on voodoo3
3. TR64 Opengl Plugin don't work it can't find his ini
4. Internal D3D7 - the one that actualy works can't run in window

The Internal sound is great!
Please fix the voodoo3 glide issue for the next release

[milen]

Opengl plugin looks realy great in Aerogauge but in most other games there are missing or white textures and sprites.
Maybe this is because of my voodoo3, but it runs realy fast and maybe it can be made opengl 1.1 compitable.

[Romboy]

May I suggest a save state system (Shift + F1-F5) and a frame rate limited assigned to one buttion like PJ64. I am getting a headache with such high framerates.

[t0rek]

What a great emulator, well but here is my bug report with this 3 games:

Super Mario 64:
- Strange glitches with the Graphic UHLE XEngine
- OpenGL Xengine Fullscreen is not working
- Flashing status bar while using Jabo's 1.4 DX7 graphic plugin

Ocarina of Time:
-DirectX is working better than Opengl while using the Xengine
-Problems with transparency textures
- OpenGL Xengine Fullscreen is not working
- Flashing status bar while using Jabo's 1.4 DX7 graphic plugin

Golden Eye 007:
-Excellent speed but...
- I can't see the sky no matter which graphic plugin I'm using
- There are no sprites using the UHLE XEngine
- OpenGL Xengine Fullscreen is not working
- Flashing status bar while using Jabo's 1.4 DX7 graphic plugin

That's all for now, guys keep up the good work

[Johann]

Originally posted by Romboy
May I suggest a save state system (Shift + F1-F5) and a frame rate limited assigned to one buttion like PJ64. I am getting a headache with such high framerates.

I don't know if this is what you are looking for, but you can use shift + F6 to save (F6 to quicksave) or shift + F9 to load (F9 to quickload).

[Doomulation]

I have a slight bug...
I haven't had any real time to test it more, though, but here it is:
Using the 0.29 beta (shouldn't matter really) of Glide64, i got a complete black screen when trying to run ssb.

When exiting uHLE, it stalled and i had to force it down.
Specs are in my sig.

[abb]

a couple of issues here

gfx plugins

(xengine)
when Direct3d mode is selected i get
ERROR eVoodoo cannot set display mode

and with OpenGL mode i can't switch to fullscreen, it just flickers and goes back to the window

audio plugins

when using uhle audio plugin (with or without internal audio plugin selected) there's no sound even though sound emulation is selected in options

using any of azimer's plugins the sound works fine but in mario the hand for selecting the save game disappears - v strange, have a screenshot.

------

specs - athlon 700, 256mb ram, geforce ddr, sb pci 128

[zAlbee]

Originally posted by abb
(xengine)
when Direct3d mode is selected i get
ERROR eVoodoo cannot set display mode
D'oh, i was wrong, its not a radeon thing. :blush: (Maybe its a Radeon and Geforce 1 thing...:) )

abb, what OS are you running?

[abb]

using win 98 se

[mightyrocket]

This is the most buggy emulator I've ever seen. Please Dominator, add the support for glide-wrappers again (not with glide64, because it's too slow), like SupraHLE!

[************]

Hi,

I have this problem with Goldeneye.

1. Using Jabos 1.5: (which I have got to work with other games e.g Starfox, Waverace). The rom loads fine, but when I start emulation I get a black screen (no sound), with the cycles going at massive rates.

2. Using UHLE plugin:

Open Gl engine: Loads rom, but when emulation started stays on rombrowser with cycles going at massive rates again.

Direct X engine:First it asks me to stop emulation first (which I already had), then when I try to load the rom, I get the error message "No plugins found at all".

My specs:
2.0 ghz P4,
Geforce 4 400mx,
256 mb DDR.

[Remote]

People please bear in mind that this is a 1st release, and things don't work as we would like all the times, I can think of a lot bigger companies with a lot more resources who have buggier software...

The uHLE2064 team consists of a lot of skilled people and if we do our best, constructive critisism and better user feedback I'm sure they will erradicate most of these baby decises... This is probaly the 1st time uHLE2064 1.0 is tested on a larger users base, with different configs and a lot of human errors... Although I haven't gotten to many errors while using it with the default config, X-engine, Internal uHLE sound plugin and N-Rage input, of course there are going to be a much wider range of errors using plugins that probaly hasn't been tested as througly. But hey, that's why we are here for...

[ScottJC]

Originally posted by mightyrocket
This is the most buggy emulator I've ever seen. Please Dominator, add the support for glide-wrappers again (not with glide64, because it's too slow), like SupraHLE!

What do you think these threads are for?
So we can help them fix the bugs.

besides i'd like to see you do better.

[Romboy]

I know that this is only on relation to plug-ins on UltraHLE but please bear with me.

My configuration in PJ64 is as follows:
Graphics: Uhle gfx plugin
Sound: Uhle audio plugin
Input: N-Rage's Direct-Input8 V2 1.82a plugin

**NOTE**
The only difference is in the configuration of both the Graphics plugin (Opengl or Direct X) and the RSP plugin (CPU core style --> Recompiler or Interpreter).
**END OF NOTE**

---------------------------------------------------------------------------------------------------------------

I have found a few interesting things that happen when trying to run several different games in PJ64.

I) Ultrahle GFX plugin
1. OpenGl Version
A- ALT + Tab doesn't work (known issue).
A1- Run in full screen causes blank screen with sound (Ctrl + T, then the option tab).
A2- Doesn’t go into full screen (At least pressing F12 would exit emulation and I couldn’t tell
A3- Untested
B- Same as below except I don’t see the small purple rectangle.
C- Same as below seems to be a sprite issue
2. Direct X 7 Version
A- ALT + Tab doesn't work (known issue).
A1- Run in full screen might or might not work (Ctrl + T, then the option tab).
A2- Always starts in full screen.
A3- F12 causes it to get out of full screen but it ends emulation and always causes the mouse cursor on the PJ64 window to disappear (I suggest to change this to ALT + Tab).
B- Higher end games (Conkers BFD, Donkey Kong 64, etc) show no graphics (only a small purple rectangle at the top of the screen) when the RSP plugin option is set to Recompiler and when set to Interpreter causes an error.
C- I have noticed on 1080 snowboarding that the n64 logo and the 1080 logo also is squashed horizontally.

II) Ultrahle Sound plugin
1. Configuration in PJ64
A- Deselect in the option to send audio list to audio plugin in the RSP configuration options.
B- Works fine, as far as I can tell.

III) Examples
1. Example for I, 2, B ---> Error box: “have not implemented RSP MF CP0 reg SP DRAM DMA address (1)” (Example from Conkers BFD).

I hope someone will find this useful. I did this pretty quick so it may have a few errors.

(!) (!) Great job Uhle 2064 team! (!) (!)

Side note: You need a logo for Uhle 2064 like Apollo's --> :apollo: .

[reapern66]

I think theres a memleak in the opengl plugin, on my voodoo 5. After I load a second game, the emu gets really lagged, takes forever just to move around in it.

[Romboy]

I have noticed a few quite strange things lately on Ultrahle 2064.

Plugins: Jabo's 1.5 video plugin, the internal Ultrahle audio plugin, and the latest verson of N-Rage's input plugin.

I for one have noticed on Jabo's plugin that for some games you have to change the size of the window. This is true at least for most of the games.

One I have found out, you don't have to do that. However there is another problem. It's on Diddy Kong Racing V1.1 EUR. It looks quite funny if you ask me. I have tried configuring the video plugin differently but everything I have tried failed.

On a side note I wonder if you could do this for other games... It would really freak out my brothers. :)

[Johann]

People please bear in mind that this is a 1st release, and things don't work as we would like all the times, I can think of a lot bigger companies with a lot more resources who have buggier software...

Microsoft... :rolleyes:

[kloud84]

Hi to everybody! i have a strange problem with ultrahle 2064 (and i had the same problem too with ultrahle 1!). To use my VOODOO1 card i have to use a glide wrapper (mglide 1246) to configure the 3dfx card, otherwise ultrahle won't work! i use the renderning engine "glide plugin" in "ultra hle gfx plugin" because i have only an ATI rage Pro card and it doesn't work very well...( i can play quite well the game, but i can't read any text that appears on the screen!). I've tryed "jabo's plugins", but "ultra hle gfx plugin" is very better! Actually I waited for ultrahle 2064 to use my 3dfx with zelda majora's mask!! Thanks to anyone who can help me to use my voodoo1 without a glide wrapper (it's very strange,isn't it?) or to make my ATI work properly!
Matteo

PS: sorry for my use of english, but i'm italian!!

[Lifeline]

i've got the same problem with my vodoo banshee. the glide
plugin that comes with uhle 2064 doesn't work well. :cry:
actually the original uhle works alot better on my banshee. (!)

but you can try using dave's glide64 plugin. works like a charm
for me. :D

anyway, to play mom you'll have to wait for 2064's next release.
because of that missing sram implementation.

hope i could help you.

lifeline

[Hacktarux]

Originally posted by kloud84
Hi to everybody! i have a strange problem with ultrahle 2064 (and i had the same problem too with ultrahle 1!). To use my VOODOO1 card i have to use a glide wrapper (mglide 1246) to configure the 3dfx card, otherwise ultrahle won't work! i use the renderning engine "glide plugin" in "ultra hle gfx plugin" because i have only an ATI rage Pro card and it doesn't work very well...( i can play quite well the game, but i can't read any text that appears on the screen!). I've tryed "jabo's plugins", but "ultra hle gfx plugin" is very better! Actually I waited for ultrahle 2064 to use my 3dfx with zelda majora's mask!! Thanks to anyone who can help me to use my voodoo1 without a glide wrapper (it's very strange,isn't it?) or to make my ATI work properly!
Matteo

PS: sorry for my use of english, but i'm italian!!

Make sure you have installed correctly a voodoo driver and remove the glide2x.dll file from ultrahle folder.

[Hacktarux]

Originally posted by mightyrocket
This is the most buggy emulator I've ever seen. Please Dominator, add the support for glide-wrappers again (not with glide64, because it's too slow), like SupraHLE!

Why don't u select glide mode in uhle video plugin ? It should be exactly the same as in the original uhle (maybe you'll have to remove glide2x.dll from uhle folder depending on your video card coz i don't know which version of this file has been put with the release, i have to ask uhle team)

[Lifeline]

by the way...
if i don't delete the glide2x.dll in 2064's directory i'm unable
to use my voodoo banshee. if i do delete i got lots of glitches.
does anyone have a clue? (is this glide2x a new one only
working on voodoo3+ or is it actually a wrapper like evoodoo?)

lifeline

[Lifeline]

oh shit... this is nearly realtime posting... :saint:

it would be nice if someone could enlighten us about
the glide2x.dll in 2064's root dir.

i got another question. why the heck do i get glitches with
2064's glide plugin and don't get any with oldschool uhle.
this is NO joke! (i know they say it's identical)

lifeline

[Hacktarux]

glitches are another thing, did u have reported it in this thread (i've just come back and i didn't have time to check yet). We have improved the uhle plugin, fixed some bugs in it added ucodes and speeded it up a bit... But there can still be a few problems

[StonedConker]

I saw in previous posts ppl having the same problem as me but din't take a well-defined answer.I speak about the xengine plugins.In D3D when i start the game i get an error message evoodoo cannot set display mode...then the emu crash.In opengl everything goes well except i cannot go to fullscreen,if i try everything messup with the rendering.In opengl also you must restart the emu if you use the plugin.It's oneuse only!.My gfx card is a GF4MX440.

....check nooneLivesForever with the open gl plugin and you'll see that the gun gfx appears correctly,something that no other plugin manage to fix.Great<_<

[Zephon]

About the uHLE Glide plugin, it's working fine for me (I have a Voodoo2). I deleted the glide2x.dll file from the UltraHLE folder. The only problem is that when I press ESC to stop a game, the GUI doesn't appear. The game image freezes, and the emulation actually stops just like it should be, but the game screen is still there. Then I press Alt+F4 to close the emulator and the screen goes back to normal.

Btw, using the uHLE Glide plugin in Zelda MoM, in the cutscenes there should be some black strips on the top and the bottom, but these black strips are pink. This also happens in the beggining, when the Nintendo64 logo shows up. THe background is all pink. This does not happen with Glide64.

[Hacktarux]

I've got the info, the glide2x.dll file is for voodoo2 cards, if u have another card, or think you have a better one for ur os/video card, please remove the one that is included with uhle2064.

[kloud84]

I've forgotten to say what's my problem with the ORIGINAL voodoo1 drivers: if i use them with ultrahle (1 or 2064), during the game (it may be the introduction or during the game) i can only see the BMPs that are in the background (for example, in Super mario 64, i can only see the picture of the sky!) and no 3d image appears...in other words,i CAN'T see all the 3d objects that usually moves during the game (is their name "Sprites"??). So I have to use a glide wrapper to configure my 3dfx card,and after making a glide2x.dll with the wrapper,telling him to use the voodoo card, i put the new glide2x.dll file into my ultraHLE directory and i can play games...

[Lifeline]

the problem i do have is texture alignment. the 3d-geo seems
to be ok. wireframe looks pretty perfect. :D

for example nearly all text boxes in both zeldas do show
alignment problems. the text itself, too. many walls....

in mario 64 mario's face texture is "shifted"... the sky is wrong
aligned. texts, too. and what looks pretty funny are the trees.
the wireframe looks cool but the textures are wrong centered.
(looks like some crazy cut-off) :)

i don't remember other things. but for me the problem with
xengine's glide is wrong alignment. the dimensions of the
applied textures seem to be right. but many of the textures
are wrong centered.

and i also have that strange pink border color. seems to be
some kind of color key!?

forgive me but i didn't try out xengine's directx and ogl. ogl and
directx is a royal pain with a banshee. :saint:

regards, lifeline

[bomb]

Using a Duron 800Mhz and a Geforce 2MX in WindowsXP, I can't run UltraHLE 2064 in fullscreen when using the ogl plugin. With the D3D plugin, it's the opposite - I can't run it in windowed mode. (Hitting F12 does nothing in both cases).
Another problem I have with the D3D plugin is that if I stop the emulation (using the esc key), the emulator crashes if I start the emulation again (using the F5 key).

Cheers and thanks for a good emulator.

[ComixManiac]

I'm using a Pentium 3 733 with Geforce2MX 400 in Windows XP. I've tested the plugins only with Zelda:Ocarina of Time so far.

Using xengine-direct3d the graphics are a little worse compared to the opengl version. The internal sound with xengine-direct3d has less chops than jabo's Direct3D7 1.4 plugin but is choppier than the xengine-opengl version! Plus the xengine-direct3d plugin runs only in full screen while the opengl only in window mode.
I'm getting the best results in graphics with Jabo's plugin. Only problem is the sound, hope that it will be fixed in next versions:)

[Dominator]

Note :

Even tho' we do not reply to all your messages, we currently read them all and really appreciate your reports.

We take good care of these helpful informations.

Thanks for your support.

[Cissou]

When I use the Glide Xengine plugin, i can't quit the game, i need to kill the emu. And every time i quit the emu normally it crash on quitting.

[straight]

Great work UHLE 2064 team! I'm playing F-Zero at high framerates for the first time on my machine (1964 has slowdowns no matter how hard I tweak the plugins, unless I just turn the audio off). Some of the 2D graphics are screwed up (no power boost meter is the only one that affects gameplay), but I'm guessing that's a known issue or one of the Voodoo3 problems folks have already mentioned.

I'm also having the problem others have mentioned with Glide64. When I switch to fullscreen, the audio works and I can hear the game responding to my blind menu selections, but the screen is completely black except for the framerate counter in the corner.

I also have a weird glitch in the F-Zero menus. After I press Start for the first time, the selection highlight moves all the way to the right, as if I were holding the controller to the right. I have to jab the left button like crazy to get it to move left (it keeps trying to move back right) and then tap the A key at just the right moment to get the selection I want. (Cool! You added a mini-game to F-Zero!)

It does the same thing in the track selection screen. The ship selection screens and the game itself are fine and don't have any controller problem. I'm using N-Rage Direct Input V2 1.81a (and yes, I'm sure I didn't accidentally configure the mouse or a key to Right). Haven't had similar problems on any other game I've tried.

I'm also getting the thing where 2064 crashes when I quit. I also get some crashes when I try to quit a rom.

[The Khan Artist]

Well, it seems all my problems have already been reported, so I'll just confirm them...

In uHLE 2064, the audio and input work just fine for me. Input is N-Rage 1.82a, sound is uHLE internal.

I've got a 16MB PCI Voodoo Banshee. I've tried Glide64 0.3, and all I get is the black screen. The game continues in the background, just no GFX. The uHLE Glide plugin works, but I get horrible texture mis-alignment problems, and in Mario64, the borders are pink (!) instead of black. I'm using koolsmoky's latest Glide2x and Glide3x DLLs on Win98 SE, w/ AMD K6-2.

Glide64 works just fine for me in 1964.

I'm much looking forward to uHLE 2064 v2! Keep up the good work!:n64:

EDIT: The "new" v3fix works to fix the texture alignment. Also, a helluva lot of stuff is pink when it is supposed to be black. A quick run through StarFox (up to the start of the first level) shows this quite clearly.

[Engeljaeger]

@ straight:
Exactly the same problem with that "mini-game" ( ;) ) here...
Also with the graphics...so that's no glide64-related problem, cuz I used uhle gfx, both, Ogl and Dx7...

[Johann]

It does the same thing in the track selection screen. The ship selection screens and the game itself are fine and don't have any controller problem. I'm using N-Rage Direct Input V2 1.81a (and yes, I'm sure I didn't accidentally configure the mouse or a key to Right). Haven't had similar problems on any other game I've tried.

I think that it's a bug of the n-rage plugin. It happens to me in all the n64 emus when I have the 2nd player pad unplugged. Plug it or try another plugin.

[The Khan Artist]

Originally posted by Johann
I think that it's a bug of the n-rage plugin. It happens to me in all the n64 emus when I have the 2nd player pad unplugged. Plug it or try another plugin.

N-Rage 1.82a works just fine for me in 1964. I DO see the problem with uHLE, so I think it's the emu, as I have exactly the same controller config in both.

[Engeljaeger]

Hm...I've noticed something...maybe it's of no importance...I don't know too much about emulation ;)
I tried different ways to get Zelda OoT to run perfectly...
Well...I found out, that no matter if I take UHLE gfx or one of Jabo's gfx-plugins (1.5, 1.4 D3D7, 1.4 D3D6)...I always get the same FPS...always around 17-20...I dunno...that seems a bit low to me but the speed seems quite good...so the only thing that's not perfect is the sound which has those stops...and another funny thing is (or maybe it's normal...I dunno) that when I have sound emulation disabled the FPS are still the same... :plain:

[MrMickey]

The mosts grafics plgin don't appear nothing.. only a black screen and a frme-rate of 10 to 12...
but nothing....

with xengine equal...

[Lifeline]

@engeljaeger

the framerates you get is fine. the n64 seems to have 50
or 60 (pal/ntsc) video interrupts. but the raw video and
proccessing power of the n64 is not high enough to render
that many frames in both zelda games. 17-20 is "normal"!

i think the sound glitches/pops derive from desync. because
uhle emulates the hardware of the n64 mostly hle and not lle.
the cycle counts are not too accurate. this is a problem with
every n64 emulator i know. in some sound plugins there's
the option "sync game to audio" which helps most of the time.

but what i don't get is why no one has ever implemented a
samplerate adjustment to sync the sound to the framerate.

cheers, lifeline

[Engeljaeger]

Aah...I as already wondering, cuz 20 FPS seemed to be a good speed :)
Well...I haven't tried all the sound plugins yet, so I might do so now...but the uhle one is the fastest, isn't it?

Thx :)

[ComixManiac]

The internal audio plugin seems to be the only that works for me! Jabo's and Zilmar's plugins produce no sound and Azimer's plugin crashes the emu:cry: So ultrahle's sound is the most correct yet:)

[Hacktarux]

Remember that you should only use hle sound plugins with ultrahle. Anyway it wouldn't make sense otherwise, coz a lle sound emulation would take way too much processor time for the machines uhle is generally designed for.

Ultrahle sound plugin and internal plugins are using the same hle code, but the sound output code is different. Internal plugin have a better sync and should be faster. On the other hand this better sync causes skip issues. The ultrahle plugin should have less skip but it's not as stable as internal one.

The only other hle sound plugin is azimer one, on my system it is also working but it has same stability issues with uhle as external uhle plugin and should also have the same sync issues..

[salk]

On this machine: Win XP SP1 - Radeon 9700 (for DirectX), Voodoo 5 5500 PCI (for Glide), Athlon XP 1900, Epox Via KX333, Corsair 512 DDRAM.

First of all: I need to delete the Glide2x.dll file or else I will always get an error "genport I/O initialization failure" (which I found out in this forum). I hope it was not important (but if it was not, why was it there ?).

Sound: Always Internal Audio solution selected for keeping stability and compatibility highest.

Controller: Alwats Nrage Plugin 1.82s

Xengine Direct X : Mario 64 works with major graphial issues. Mario Kart, ISS 98, ISS 2000 causes a black screen to appear. Not working. Diddy Kong Racing: works with massive graphical problems.

Xengine Glide: ATTENTION: Cause severe Windows problems!! It locks the system and it messes with internal peripheral's drivers! Extremely buggy and dangerous!! I had got bad consequences by this. To the developer team: NOT RECOMMENDED to include such a plugin at this stage.

Various - In Zelda Ocarina of Time: Error : Cant open SRAM

[Hacktarux]

the glide2x file is the "driver" of the voodoo card. The one included with uhle is the voodoo2 version. We have included it because the emulator can't start on a system that don't have it, i'm thinking about a few tricks to solve this problem in the next release...

Concerning the glide renderer stability, it's the original uhle one, and from what the team have seen it's enough stable on voodoo2/voodoo1 cards.. Maybe in the future we should program a voodoo3/4/5 renderer, we'll see, it's not the main problem currently but don't worry we are preparing something :)

[salk]

Thanks for the reply, Hacktarux! I wish you the best in your hard job. You see...DirectX and OpenGL have a lot of supporters. Quite already many plugins for them and there will be no lack of them neither updates. I am very concerned about Glide instead. It deserves the same attention, according to me. Dave did a great job and Gonetz is keeping it up wonderfully. Indeed I'd be extrememly pleased to have you developers of UltraHLE surprise me with your new rendering engine. I hope you can also fix those other big problems I have met as I tested the executable with the few games I legally own. Again: best of luck to you. One more thing: when I push "ESC" I go back to Windows but it doesn't bring the screen resolution back as it originally is. In order to get to that, I do need to quit the emulator. Perhaps you can find a way to fix this too. Keep it up,guys!

[The Khan Artist]

Originally posted by Hacktarux
don't worry we are preparing something :)

Hmm...:happy:

As for the Glide plugin not working on newer Voodoo cards, have you guys figured out the problem with Glide64 0.3?

[Johann]

Hmmm... I think that there was a special ultraHLE glide2x.dll fix for voodoo3 and newer 3dfx cards. Maybe it can help some of the users that have gfx problems.

(I think that there was a banshee fix too, but i'm not sure...)

[reapern66]

the fix was for the dll, not the hardware. Im hopping the new release will be based on todays drivers. Otherwise nothing or everything will work for different people.

[The Khan Artist]

Originally posted by Johann
Hmmm... I think that there was a special ultraHLE glide2x.dll fix for voodoo3 and newer 3dfx cards. Maybe it can help some of the users that have gfx problems.

(I think that there was a banshee fix too, but i'm not sure...)

The so-called "Voodoo 3 fix" was a sort of Glide wrapper that adjusted texture alignment for newer cards. That's all.

[The Khan Artist]

A couple more problems.

System: Celeron 700, Intel i810 mobo w/ integrated gfx chip, Windows 2000 SP2, DirectX 8.1.

Yah, I know the i810 sucks, but this is a sub-micro system I picked up for cheap, and it's worth the 50 bucks I payed. It has no AGP or PCI slots so I can't stick in a decent card.

The only game I have tested is Super Mario 64.

1) I'm using the uHLE DX7 plugin. It starts and goes fullscreen, and it does NOT hide the mouse. And since it changes the res, maximizes the uHLE windows, and *then* inits the gfx, I'stuck with a blinking part of a double-headed arrow cursor no matter which side of the screen I move the mouse to.

2) In Mario, in the startup screen, Mario's head is black and gray, instead of colored.

3) In that same screen, the top and bottom borders are a mixture of black and pink.

4) When entering a level, the background is black, preventing you from seeing the star description text.

5) There are weird problems with the edges of some polygons, where the depth isn't right, and the polygons show through each other.

Screenshots are attached.

EDIT: split part of this into the misc problems thread.

Screenshot for 2 and 3:
http://users3.ev1.net/~mebane437/bscap0.jpg

Screenshot for 4:
http://users3.ev1.net/~mebane437/UltraHLE 2003-01-03 19-42-00-77.jpg

[Lugia]

When triying to play any game with the Glide selected at the xengine it says: "Genport I/O Initialization Failure"

Running it in win2k SP3, V3 3000 wit the lastest x3dfx drivers, d3d works fine

[The Khan Artist]

Originally posted by Lugia
When triying to play any game with the Glide selected at the xengine it says: "Genport I/O Initialization Failure"

Running it in win2k SP3, V3 3000 wit the lastest x3dfx drivers, d3d works fine

Delete the Glide2x.dll file in your uHLE folder.

[Quvack]

Originally posted by The Khan Artist
A couple more problems.

System: Celeron 700, Intel i810 mobo w/ integrated gfx chip, Windows 2000 SP2, DirectX 8.1.

Yah, I know the i810 sucks, but this is a sub-micro system I picked up for cheap, and it's worth the 50 bucks I payed. It has no AGP or PCI slots so I can't stick in a decent card.

The only game I have tested is Super Mario 64.

1) I'm using the uHLE DX7 plugin. It starts and goes fullscreen, and it does NOT hide the mouse. And since it changes the res, maximizes the uHLE windows, and *then* inits the gfx, I'stuck with a blinking part of a double-headed arrow cursor no matter which side of the screen I move the mouse to.

2) In Mario, in the startup screen, Mario's head is black and gray, instead of colored.

3) In that same screen, the top and bottom borders are a mixture of black and pink.

4) When entering a level, the background is black, preventing you from seeing the star description text.

5) There are weird problems with the edges of some polygons, where the depth isn't right, and the polygons show through each other.


Problem 1: Yep, thats just how the plugin is for now.

Problems 2-5: My older machine has a i810 in it. The only time that I had graphics errors like that in your screenshots, was when I was using the default i810 drivers that came with Windows. Once I'd updated to the latest from the Intel support website, the graphics and speed were both pretty acceptable.

[salk]

Hello! My computer is pretty new (Athlon 1900 and Radeon 9700) and I am having number "2" problem too using DirectX plugin plus that the graphic is all messed up (is it the so called "clipping" not working ?) so I doubt it's a matter of driver updates since mine are the newest (both VIA's and ATI's and everything else as well). Regards! :saint:

[MastaG]

The Voodoo3AGP gave me more fps at games like Q3 but ut2003 gta3 and most others didnt work so i decided to put back my GeForce2. OS: WinXP Pro Specs: AMD Athlon 2400+ 512DDR333 geForce 2MX400 AGP + 3Dfx Voodoo 1 (addon card).

Audio: Only uhle audio plugin with and internal audio seems to work all other plugins make the emu crash after a rom is loaded.

Video: OpenGL has strange texture problems, some textures are black (the press start text at mario title screen) and som textures will be invisible when looking at them from some point (the castle during intro of mario64) fullscreen aint possible.
D3D: Has the same problem i get when i enable FAST ALTERNATE Z BUFFER in eVoodoo.
Glide: Can't test it because there arent working Voodoo1 drivers for XP (voodoofiles.com do have 'm but the voodoo.cab is damaged)

Speed is great and I dont have audio stuttering.

[The Khan Artist]

Originally posted by Quvack
Once I'd updated to the latest from the Intel support website, the graphics and speed were both pretty acceptable.

I have the latest ones already. I made sure all my drivers were updated before posting bug reports. Oh, well. If nobody wants to support the 810, I understand.

[ChaosBlade]

Note: Mainly tested with OGL plugins , since i have a geforce 2 card :)
so i apolegize for 3dfx users :)

anyway, here we go :

My Config :
- Xengine OpenGL .
- Internel Audio .
- NRage's Dinput plugin 1.82 .
- System Spec's in sig .

Graphics :
- General Alignment Problems in various games , with almost gfx plugin i tried .
- General Problems with Xengine OGL , such as small graphic distorts , and no full screen .
other OGL plugins dont work at all :
- 1964 OpenGL is very very glitchy here .
- TR64 OGL asks for Ucode then locks up at setup .
- Jabo's plugins work after the DLL fro PJ64 is copyed over .


Audio :
- So far , no audio plugin except from internel worked . Testing this atm .
- Internel Audio Works perfect , a little cracky , but thats just my celeron crying ;)

Controller :
- nRage's works perfect after i config'd the mempak right .

ps: about the FPS thing , i have 61FPS in some really graphiclly-easy spots ,
such as the nintendo logo over the black background

Will continue to test with the little selection
i have (Mario,Zelda OoT & MoM, Starfox and a few little more)

[tyrael64]

Using UHLE glide plugin, I got some errors:

-In Pokemon Stadium, menus are all messy, but ingame grafics are ok.
-Mischief Maker don't even start, giving a error in uhle_video.dll

also, the same error with texture alignment that happens in Uhle(the first one), occur in Uhle2064, even when I put the v3fix...




My spec...

Celeron 600Mhz, Voodoo 4 AGP, 192MB RAM DIM
hd quantum bigfoot and another newest...

[Tri-Force]

my controler configures but wont work in the game. all the buttons work but the stick wont move the link or any of the functions on the screen. haven't tried any other game as of yet and i am running this on my BRAND NEW COMPUTER BABY!!!!!!! (i'm a little excited) which is a Athlon XP 2000 running on WinXP and using the supplied controler plug in