|
|
#1
|
|||
|
|||
![]()
Hi everyone,
I'm currently using Project64 2.2 and now I want to install the new 2.3 release. But, as some games need specific settings to fix glitches, I would have to change the settings all over again in the new version. Is there some way I could import my current per game configurations into the 2.3 version? Thanks in advance. |
#2
|
|||
|
|||
![]()
all your user settings are in project64.cfg, you can just backup this file and copy it over the top of the new one.
What changes you have that are not there by default? |
#3
|
|||
|
|||
![]() Quote:
![]() Well, I'm using the 2.2 version, so I don't know if any of these issues have been fixed on version 2.3, but the changes I did are things like setting the VI Refresh Rate to 1475 on Perfect Dark so it wouldn't run too fast, enabling "Read Every Frame" on Glide64 for Mario Kart 64 to fix the big screen in the Luigi's Raceway course, and also various tweaks on Donkey Kong 64, among other things. I don't have too many games, but it just would be easier to copy the configuration file to the new version. By the way, I've found all these fixes through various sites online, and the latest Project64 GameFAQ I've found is for version 2.1. Is there a GameFAQ for the 2.3 version, or a PJ64 wiki where I could find issues and fixes for the current version? |
#4
|
|||
|
|||
![]()
Unfortunately smiff was the one who did all that and he is long gone. I do want to spend some time soon to re-do the website and add a wiki here to start to fix up the documentation.
|
#5
|
|||
|
|||
![]() Quote:
![]() Quote:
![]() I'm currently using the latest GlideN64 revision which I think is a great plugin, but I'll give Jabo's 1.6.1 a try. Thanks! |
#6
|
||||
|
||||
![]()
If you can run GLideN64 full speed, I recommend using that instead. I cannot, it's far too slow for me. If you need performance, use Jabo's 1.6.1.
|
#7
|
||||
|
||||
![]()
But turning off frame limit makes framerates really choppy,at least on my end with a certain older PJ64 version for all my code hunting needs.
|
#8
|
|||
|
|||
![]() Quote:
http://pj64wiki.com/ |
#9
|
||||
|
||||
![]()
All you have to do is create a branch named gh-pages and put an index.html in it. Then http://project64.github.io/project64/ will become a valid URL and you will have a website.
So like: Code:
cd ~/project64/ git checkout -b gh-pages git add index.html git commit -m "lol website" # Upload the website: git push origin gh-pages
__________________
http://theoatmeal.com/comics/cat_vs_internet |
#10
|
|||
|
|||
![]()
https://github.com/project64/project64-wiki
I will be using that, so all edits to the wiki will go through github pull requests |