PDA

View Full Version : A couple more issues...



Legend
January 4th, 2004, 00:20
1. Is the Conker flicking caused by the emu and can't be fixed until MAYBE the last realease? I'm using Jabo's .

2.In Yoshi story, the sprites (yoshi and enemies) are invisible using Jabo 1.5.1 and of course it looks fine in PJ64.

3.In the World is Not Enough, it freezes after about a min or two despite what plugin I'm using. I tried changing what I could (CF, 32 bit, etc.) but so far, nothing works. I'll spend some more time playing with the self-mod. I think. But is that the main reason why games lock up (self-mod issue). Because I'm having similar problems with with the Tony Hawk's, worms, Turok 3 and Duke Nukeem.

4. Is there a way to change the size of the rom browsers lists because I really like being able to see all my games at a glance instead of scrolling through my 60 games. And also is there a way to prevent the browser from expanding to the sides and just basically moving around when I change vid plugins?

5.F-Zero runs about 50% slower than on Pj64 using Glide64 on my Voodoo 2. The game ONLY looks good using Glide64 that's why it kinda sucks. It also gives me a strange message "Is the memory expansion pak inserted correctly?" whenever I start the game. I switched it to use the pak but the game does not start then.

I trully do apreciate any help here so I can finally fully cross over to the 1964 world from the slow PJ64 realm which I've been apart of for years.

Legend
January 5th, 2004, 01:58
C'mon guys. There's alot of big issues here with some big games and this might help others of course. Not a single response, tip, advice, solution nothing. Yet every other thread gets tens of answers no matter what the question is. I've been apart of n64 emulation for years and I know what I'm talking about here and I'm being very nice. No one else plays yoshi, conker or tony hawk or f-zero or Turok.
Pleeease guys I need some help here. Trotterwatch or Clements-where are you homeys? :(

Trotterwatch
January 5th, 2004, 02:29
I will try to answer, but I can't offer too much help I'm afraid.


1. Is the Conker flicking caused by the emu and can't be fixed until MAYBE the last realease? I'm using Jabo's .

I have seen this issue before - but in the latest version usings Jabos D3D 1.5.1, it doesn't occur. The latest Forcewares seem to have broken quite a few N64 emulation related things so perhaps it is the card.

Try going into Jabos plugin though and forcing normal blending, see if that helps any.


2.In Yoshi story, the sprites (yoshi and enemies) are invisible using Jabo 1.5.1 and of course it looks fine in PJ64.

Odd, last I checked this was fine also. Does anyone else have this bug? One suggestion, go to the uninstall folder in 1964 and remove double click on the remove all registry entries script. That may help - maybe not, but it's worth a try.

3. Out of those games you have listed I completed all 3 of the THPS skaters twice each, and didn't notice any freezing issues. Though once in a while on load state there would be a problem with disappearing audio. On Turok 3 during testing I had 1 lockup, which was promptly fixed upon enabling Use 32bit.

4. Not sure, I can't think of a way to do these things. Sorry :(


5.F-Zero runs about 50% slower than on Pj64 using Glide64 on my Voodoo 2. The game ONLY looks good using Glide64 that's why it kinda sucks. It also gives me a strange message "Is the memory expansion pak inserted correctly?" whenever I start the game. I switched it to use the pak but the game does not start then.

The message on startup is a known issue. Having said that the 50% slowdown is strange - does changing settings in Glide64 not help any?

I am really sorry I can't offer any concrete help other than do an uninstall and possibly downgrade a driver version (whether you do that is of course up to you, and whether any PC games you run will be impacted by the downgrade).

jdsony
January 5th, 2004, 10:48
I'm not sure what you are looking for with the Rom Browser list. Wouldn't it be hard to read the names of the games if they were all on the screen at once? The font would have to be quite small.

I'm gonna try out the games you are having problems with and see if run into the same issues.

Legend
January 5th, 2004, 20:31
I'm not sure what you are looking for with the Rom Browser list. Wouldn't it be hard to read the names of the games if they were all on the screen at once? The font would have to be quite small..

Not really PJ64 is just a tad smaller but plent readable-it also does'nt have those little icons so that may be apart of it because on .85 I could see all of them (I think). But it just damn annoying how the browers triples its size and expands out to the sides creating a LOT of white space everytime I change vid plugins.

UPDATE:

Yoshi is working now I applied "Normal Blending"-there's trails now the menu leaves but no biggit.

Worms started working with Jabo's( I was trying to use glide64 because it's said to be fine.

Turok 3 had to be set to "Check DMA only" to work realiably (enable 32bit did'nt help).

Tony 1 works but along with a couple others I mentioned, it only works right if I play when I first start the emulator or else it will freeze.

F-zero runs perfect now but it HAS to be 640x480. :yucky:

So 5 more and i964 will be perfect for me. World is not enough still freezing. The first Duke Nukeem still freezes intermittently. Conkers still looks ugly (is there any special Jabo setting that might help like in the LAST tab of the dialog?).Tony 2 STILL feezes on me - half the time it won't get past the opening screens but when it does it 100% of the time freezes on me at FRANCE (level3) when I get graded by judges. Maybe you guys can show me you rom settings. And LASTLY( this is the WIEEEERD one) i forgot to mention, but in Star Wars Shadow of the empire in the jet bike level (stage 4 i think) randomly but every time, the graphics disappear and I'm thrown into the middle of a white whirlwind. I can still move around but only in the confinds of the whirlwind and musics still going and everything. This happens with every vid. plugin. It makes this game unplayable of course. Let's see one of you try to explain THAT.

rcgamer
January 5th, 2004, 22:04
well, for conkers im using an fx 5200 with the latest forceware driver , jabos d3d6 1.5.1 and schibos audio. in jabos all advanced settings turned off, triple buffering and 2x antialiasing, in rom settings d3d always, and force emulate clear. it works almost perfectly (the only problem is when i die sometimes i have to restart the emu because the game freezes.)

Clements
January 5th, 2004, 22:31
I can't believe F-Zero has a problem. I pay it 1152x864 with 4xAA with 1964 0.9.9 with Glide64 0.5 + eVoodoo 3.99 Beta and it actually runs slightly too fast and all the cars are the correct colours and such. It should be faster for you since you just use Glide64.

The Expansion Pack message is a glitch with the 64DD hook I believe, since F-Zero on it's own does not require the exp. pack, but the 64DD Version (that works with the F-Zero cart) does.

Legend
January 6th, 2004, 00:09
Thanks RCgamer but I tried all that on my lunch break but it still has that wired flickering. Maybe it's my video card settings?
I don't think its the CF either-I've played with that alot.

rcgamer
January 6th, 2004, 00:18
cf on default setting. you know when i first played it, it did the same thing but for whatever reason it just started working. when i got it working i enabled the rsp (guess i should have said that in my first post.)

rcgamer
January 6th, 2004, 00:50
oh yeah and make sure you have the combiner type set to 4 stage combiner.

Legend
January 6th, 2004, 01:15
oh yeah and make sure you have the combiner type set to 4 stage combiner.

Ummm, I really have no idea what you are referring to here. Sorry. I've thought about for a while here but I just can't figure out what your talking about. I hope you respond shortly because this is going to drive me crazy. :x

rcgamer
January 6th, 2004, 01:26
doh , nm that was for rices plugin. sorry. I just had a brain fart. lol

RJARRRPCGP
January 6th, 2004, 08:07
I have seen this issue before - but in the latest version usings Jabos D3D 1.5.1, it doesn't occur. The latest Forcewares seem to have broken quite a few N64 emulation related things so perhaps it is the card.


That reminds me of the fact a while ago, with my GeForce2 MX200 32 MB video card, Detonator 41.09 causes texture corruption with the snowboards under Snowboard Kids 1.

Legend
January 6th, 2004, 09:00
Well I've fixed Duke and TWINE ny changing the self-mod to Qword or whatever. Unfortunately, when I close the game I get that "execption in emulation thread" error and crahses the emulator. :(

3 more to go. So no ideas on Star Wars SOTE. You know I f-ing hate that level anyway so maybe someone could give me a save state or a save past the bike level (whose timing has to be off with how insanely fast it is despite whatever setting I use). Thanks.

Legend
January 6th, 2004, 09:56
Well I freakin fixed Conker's finally. You HAVE to use shibo's sound. Using JAbo's and the RSP causes the horrible flicking which is really wierd if you think about it.Thankfully his audio works just fine. I can't believe no one else encountered this or knew how to fix it like saaaayyy Shibo or Rice. ;)
Then I had some wired lines spewing all over the screen from the characters-fixed by turning off 32 bit.

2 MORE!!!(One more maybe if I can get a Shadows save). :bouncy:

Clements
January 6th, 2004, 10:05
Well I freakin fixed Conker's finally. You HAVE to use shibo's sound. Using JAbo's and the RSP causes the horrible flicking which is really wierd if you think about it.Thankfully his audio works just fine. I can't believe no one else encountered this or knew how to fix it like saaaayyy Shibo or Rice.

I hereby nominate this discovery for the 1964 0.9.9 FAQ Thread! You are dead right, schibo's (and only schibo's) can be used with CBFD. ;)

karth95
January 6th, 2004, 15:21
well, lemme put it this way: we tested the games with schibo's sound cause that's what the emulator comes with. It's really best to assume that that's what the games will work best with. If a game says "Use Rice's 5.2.0" it means that the game will work, possibly ONLY with rices 5.2.0.

The rest of the games will most likely work with either rices or Jabo's 1.5.1 , and I use rice's as my default, but I have a GForce card. People with radeons should probably use Jabo's. Per rom plugin settings make this so much nicer, as you can use Rice's for some games, jabo's for others, and not have to swap defaults non-stop.

rcgamer
January 6th, 2004, 18:32
well, for conkers im using an fx 5200 with the latest forceware driver , jabos d3d6 1.5.1 and schibos audio. in jabos all advanced settings turned off, triple buffering and 2x antialiasing, in rom settings d3d always, and force emulate clear. it works almost perfectly (the only problem is when i die sometimes i have to restart the emu because the game freezes.)


you figured that out all by yourself huh? :blink:

however with my setup it works with or without the rsp. in fact almost all the games i have are working fine if i leave the rsp enabled (and yes i know i dont need it unless i use jabos sound)

Legend
January 6th, 2004, 18:45
you figured that out all by yourself huh? :blink:
Yes. It's audio, who would think that would cause flickering. I disregarded that obviously like any one would. You also told me TO enable the RSp and ussse a stage 4 combiner. :P
Your post did inspire me after staring at it for hours trying to figure out why it's perfect for you and not for me. So I guess without you I would never have figurered this out.

rcgamer
January 6th, 2004, 18:49
doesnt matter really. glad you got it fixed. :1964:


P.S. stupid brainfarts, lol :happy:

Allnatural
January 6th, 2004, 19:09
Conker's does work with Jabo's audio if you enable "sync game to audio." No flickering, and the quality is better in my opinion. There is an occasional stutter in the VI/s, but I've noticed the same thing (though less frequent) with schibo's.

Legend
January 7th, 2004, 03:46
Alright fellas, I AM DONE!!! 1964 is now perfect along with ALL of my 60 games (or as perfect as you can with what emulation stuff is out currently). The glitch with Shadows and the freezing in Tony 2 were solved by what else, turning off Jabo's audio and switching to Schibo's. So apparently no matter WHAT your problem is it might help to switch to Schibo's audio in 1964 (.99 at least) orrrrr using "sync to audio" in Jabo's settings. Thanks by the way Allnatural-Jabo's audio does work with Conker and sounds better. After 6 days I'm DDDDDOOOOONNNNNEEEEEE!!!!!!!!!! :bouncy: :bouncy: :1964: :1964:
:1964: Rocks!!

rcgamer
January 7th, 2004, 04:15
yeah that (jabos 1.5.1 and schibos audio) quickly became my default config. I use rices plugin for the games that specifically state to use it. jabos d3d7 is a little better with some of the games as well. Ive gotten probably 99% of the playable games to work now And not just run but look pretty good as well.

HAPPY GAMING.

karth95
January 7th, 2004, 04:30
I dunno why, but people seem to assume that we were joking about schibo's audio. It ROCKs. It's GOOD. It really is. No joke.

Allnatural
January 7th, 2004, 04:43
I dunno why, but people seem to assume that we were joking about schibo's audio. It ROCKs. It's GOOD. It really is. No joke.
I agree, but in my very subjective tests, Jabo's just sounds better in most cases.

Legend
January 7th, 2004, 04:55
I agree, but in my very subjective tests, Jabo's just sounds better in most cases.

Yes it is in my subjective testing also.

karth95
January 7th, 2004, 05:08
there are some issues with it. its got some unimplemented features, but it is a good plugin. And it lets a lot of games work really really well.

ggab
January 7th, 2004, 05:38
in zelda OOT with jabo's sound with the option sync game to audio enabled its sound better, because with the default (schibo 1.2 one) for example in the opening the music cracks or is interrupted/cut for a few 5/10 miliseconds, this happend also if the jabo's ones is not set to sync game to audio, any solution?
i know that schibo plugin not come with the sync option...
from my machine the only hardware thar it could be the problem is my integrated sound card, CMI8732/C3DX PCI audio device from the asus A7V-266-C mobo.
a sound buffer problem?
that's all for now, bye