#21  
Old 13th September 2009, 04:32 AM
michaelptrinh michaelptrinh is offline
Junior Member
 
Join Date: Sep 2009
Posts: 27
Default

The next time (hopefully there won't be a next time with N-rage's DirectInput8) the error pops up during emulation, I'll copy what it says in the box.

But here was what was recorded in the logs:
[7:55:49 PM 12/9/2009] Error 0x80040154 - device creation
[7:55:49 PM 12/9/2009] Error 0x80040154 - device creation
[8:06:25 PM 12/9/2009] Error 0x80040154 - device creation

I don't know if this helps.
Reply With Quote
  #22  
Old 13th September 2009, 02:39 PM
HatCat's Avatar
HatCat HatCat is offline
Alpha Tester
Project Supporter
Senior Member
 
Join Date: Feb 2007
Location: In my hat.
Posts: 16,236
Default

N-Rage's plugin also has better support for newer devices.
(I noticed from your upload that we don't both use the keyboard; otherwise most plug-ins could work fine.)
Reply With Quote
  #23  
Old 15th September 2009, 02:31 AM
michaelptrinh michaelptrinh is offline
Junior Member
 
Join Date: Sep 2009
Posts: 27
Default

Hey,

I was wondering if all N64 emulators use .eep format for auto saves? Can I use my auto save from PJ64 on 1964, for example, or any other N64 emulator?

Same question for PJ64 savestates.
Reply With Quote
  #24  
Old 15th September 2009, 02:48 AM
HatCat's Avatar
HatCat HatCat is offline
Alpha Tester
Project Supporter
Senior Member
 
Join Date: Feb 2007
Location: In my hat.
Posts: 16,236
Default

Good question, no for save states, with the exception of 1964's buggy support for save states made by Project64 1.4.
Save states actually contain quite a portion of the game's binary, but there is still what is unique based on the emulator writing them. You also can't load a save state created with Project64 1.6 on the 1.5 version, but you can do so in the other direction i.e. load save states created by older versions of the emulator.

EEPROM saves (EEP) have a couple main different file sizes, though many N64 games use this format. Other possibilities are SRAM (SRA) and FlashRAM (FLA).
As for the controller/memory pak saves (MPK) those are dependent actually to the controller plug-in we use of course.
The format is decided by the game technically, but the emulator is sometimes configured to force a certain format.

These "battery save" formats however are certainly dependent to the game, but to transfer them for other emulators like 1964 to use, you need to know what the file name of the EEP/SRA/FLA/etcetera save would have been if 1964 had created it. From there, just rename the one Project64 made to the file name 1964 uses, and it will load.

Last edited by HatCat; 15th September 2009 at 02:50 AM.
Reply With Quote
  #25  
Old 15th September 2009, 04:03 AM
michaelptrinh michaelptrinh is offline
Junior Member
 
Join Date: Sep 2009
Posts: 27
Default

I get it. Thanks!
Reply With Quote
  #26  
Old 20th September 2009, 03:28 AM
michaelptrinh michaelptrinh is offline
Junior Member
 
Join Date: Sep 2009
Posts: 27
Default

I was playing Mario Party 3 and the game crashed like maybe 3 times but worked fine thereafter.

According to the Logs folder, the problem was a Direct3D8 error:
[9/19/2009 6:39:58 PM] SetViewport (scissor) failed 8876086C (0,484,640,-4)

Is there a better plug-in that would prevent this error from occurring?
Reply With Quote
  #27  
Old 20th September 2009, 03:29 AM
michaelptrinh michaelptrinh is offline
Junior Member
 
Join Date: Sep 2009
Posts: 27
Default

I also have 1964. Is that a more stable emulator or does it depend on my computer?
Reply With Quote
  #28  
Old 20th September 2009, 04:14 AM
spencerhasty05 spencerhasty05 is offline
Junior Member
 
Join Date: Sep 2009
Posts: 2
Default

hey im new were do i find downloads
Reply With Quote
  #29  
Old 20th September 2009, 05:14 PM
HatCat's Avatar
HatCat HatCat is offline
Alpha Tester
Project Supporter
Senior Member
 
Join Date: Feb 2007
Location: In my hat.
Posts: 16,236
Default

The game is fine on 1964. The real concerns in stability are more game-dependent, and pretty much every emulator does something better that another doesn't.

For that issue there are many better plug-ins, but here's a quick restore to the results you got for Project64.

With 1964 you can hit Ctrl+P to change plug-ins.
This reads files from the "1964\Plugin" folder. If you want both emulators to be able to use Jabo's Direct3D8 1.6 (from Project64), find the DLL for that plug-in from "Project64\Plugin", and copy it over.
Reply With Quote
  #30  
Old 21st September 2009, 02:27 AM
michaelptrinh michaelptrinh is offline
Junior Member
 
Join Date: Sep 2009
Posts: 27
Default

Are you saying that the instability of the game is due to the emulator and not the plug-in? So in this case, using 1964 instead of PJ64 to run MP3 ought to fix the crashes?

And, I don't understand why the same graphics plug-in should be used if there are better ones for this problem. Is there any advantage to switching to a better one?
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT. The time now is 04:28 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.