PDA

View Full Version : How can I get 1.7 source or leaked?


theboy181
16th February 2017, 04:48 AM
How can I get 1.7 source or leaked?

ExtremeDude2
16th February 2017, 02:29 PM
It was at some point, I don't know where to find it again. Why do you want it?

theboy181
17th February 2017, 01:38 AM
request from a user..

zilmar
17th February 2017, 06:00 AM
it should all be in the history at github

HatCat
25th February 2017, 05:37 AM
weed request..

1.7 wasn't even "leaked" to the other developers of Project64 besides zilmar at the time. ExtremeDude2 was thinking of the 1.6 source leak from hcs.

Anyone here around 2011 at the latest would had to have been around to know that, but then RPGMaster I guess is relatively new. You're free to correct me if that's not the user you're referring to. :p

retroben
25th February 2017, 11:33 PM
You wouldn't happen to be referring to 1.7.0.50 ver23/b23 would you? :p

I got it a long ways back originally from EmuCR's leak on a whim.
Later on,some spanish site called Emudigital which died then changed to EmuDesc,has that particular version as of the last time I checked many months ago.
Before and when it was on Emudigital,there was a massive cheat list in it,now I am stuck (new laptop re-download) with a different list full of cruel encrypted Xploder codes,forcing me to either look for the code or go online to decrypt it via Gamehacking[DOT]org instead of just having the codes and their values.

Problem is,now they have that stupid login requirement for links,so you will have to do some digging while attempting to reach a print-only or cached version that doesn't have them hidden,I had to do that and get lucky enough to find the right file within one of the file upload sites it used.

Hope this info is helpful. :)

Edit: NINJA'D

I found another place that seems to have it now with other more standard versions listed with it.

http://sm64hacks.com/thread-97.html

I also dug up what appears to be the 2shared copy I found last time,but I won't post it directly at the moment just in case.

Edit 2: BTW the 2shared copy was uploaded on 2012-04-20.

ExtremeDude2
25th February 2017, 11:34 PM
Anyone here around 2011 at the latest would had to have been around to know that, but then RPGMaster I guess is relatively new. You're free to correct me if that's not the user you're referring to. :p

Shots fired

HatCat
26th February 2017, 12:14 AM
You wouldn't happen to be referring to 1.7.0.50 ver23/b23 would you? :p

No, I was referring to 1.7.

Pretty much every version of Project64 1.7 was leaked; I don't care about that. I'm surprised you managed to find only one version and not more. I'm just saying, there's no such thing as a source leak to any versions of 1.7.

retroben
26th February 2017, 01:08 AM
Well I know there was one on GSHI claiming to be 1.7.0.55 though,so that's another build.

I just didn't dig around for any random version,it was timing that nailed me b23 from that one day it was briefly available before being taken down. :)

Edit: Also,got a little sick today,so that's why no codes or anything.

RPGMaster
26th February 2017, 05:42 AM
That request wasn't by me lol. zilmar has already mentioned in the past that the source for 1.7 is available anyway :D .

I can't think of a reason to even use 1.7 at this point. I like sticking with 2.x at this point.

retroben
26th February 2017, 08:19 AM
Earlier 2.x versions: Savestates prone to crash,other things crash easier,and realtime cheat functions are trashed.

Current 2.x version/s: Behaviour changes that go against my code hunt methods,savestates still may be sketchy,and realtime cheat functions are STILL trashed despite the few mentions of a fix that Mupen64Plus (M64+ AE) has that works splendidly.

The realtime cheat fix would prevent the need of savestate spamming so often,while also noting its now impossible to use that method because the memory viewer closes upon loading a savestate,making the fix for realtime cheats not as good for anything more than better codes that are already found and risky attempt combos before loading back to a stable game state,provided it doesn't crash randomly.

Also,the site I linked seems to even have the ancient versions of PJ64 as well,so that is pretty nice if anyone wants to check them out for some fun,or for in-depth testing of various things.

That is if they even open/don't BSOD on Windows 10... :(
Guess that could be avoided by VM or Wine or whatever else runs stuff with mostly full feature access in simulated older Windows OS version programming.

RPGMaster
26th February 2017, 06:47 PM
Earlier 2.x versions: Savestates prone to crash,other things crash easierI don't recall having any significant save state issues besides some audio stuff and other miscellaneous things I improved :D . I guess there are still games like turok with potential problems, but simply pressing F7 a few extra times isn't the end of the world. I bet 1.7 has the same issue in Turok anyway.

Current 2.x version/s: Behaviour changes that go against my code hunt methods,savestates still may be sketchyCan you elaborate on this? What changed? I'm pretty sure that the savestate functionality is better than any previous version of PJ64.

The realtime cheat fix would prevent the need of savestate spamming so often,while also noting its now impossible to use that method because the memory viewer closes upon loading a savestate,making the fix for realtime cheats not as good for anything more than better codes that are already found and risky attempt combos before loading back to a stable game state,provided it doesn't crash randomly.Honestly, I'd rather just use Nemu for making cheats. It is far better suited for that task, if the game actually works :D . I bet Nemu has better performance than 1.7 too.

That is if they even open/don't BSOD on Windows 10... :(
Guess that could be avoided by VM or Wine or whatever else runs stuff with mostly full feature access in simulated older Windows OS version programming.Bruh, do you even use the newest version of PJ64?? The BSOD issue has been solved a while back. I haven't seen any complaints since then.

retroben
26th February 2017, 07:55 PM
The last part,I was talking about the ancient versions for 1.5 and older,down to the earliest 1.0 version to test for interesting results,there is a higher risk of crashing to a BSOD than 1.6 and newer.

I missed out on the 1.0-1.5 days,so it would've been interesting to see it run on Windows 7 or even Windows XP while Win10 might keel over on even older versions for whatever odd reason,even though the Win10 side of PJ64 problems has also been fixed.

RPGMaster
26th February 2017, 08:07 PM
The last part,I was talking about the ancient versions for 1.5 and older,down to the earliest 1.0 version to test for interesting results,there is a higher risk of crashing to a BSOD than 1.6 and newer.

I missed out on the 1.0-1.5 days,so it would've been interesting to see it run on Windows 7 or even Windows XP while Win10 might keel over on even older versions for whatever odd reason,even though the Win10 side of PJ64 problems has also been fixed.My bad :D . I'm sure 1.4 - 1.6 were fine though.

HatCat
28th February 2017, 03:38 PM
Well I know there was one on GSHI claiming to be 1.7.0.55 though,so that's another build.

I just didn't dig around for any random version,it was timing that nailed me b23 from that one day it was briefly available before being taken down. :)

Edit: Also,got a little sick today,so that's why no codes or anything.

Still don't care.

Still was talking about 1.7, not 1.7.0.55. There were no source leaks to 1.7.anynumberyouwanttoputhere.

The binary builds themselves being leaked became quite a popular thing to do for every single version after the point in time at which cracking the protection became little more nuisance than monotony.

That request wasn't by me lol.

Even if you're not aware of that request being by you, it still is when grandmother theboy181 says so.
Like that pizza you wanted so badly in order to make DLLs.

Think about it. "request by developer" would make more sense, but what "user" in its broadest terms would want the source to an outdated version? Wouldn't it be more persuasive to call it a developer, in order to get people to send the source? Except that would be too constrictive of the possibilities...if he had said that, then who else but you? If instead he should say "user", then it could be either you, or, well, just a recursive evasion to ExtremeDude's question by answering "Why do you want it?" with "Request from myself."

zilmar has already mentioned in the past that the source for 1.7 is available anyway :D .

If you can figure out which SVN ID corresponds to which, then yes.

It doesn't matter though, not now. Back then 1.7 source was a very big deal since there were no updates to Project64, 1.6 was ancient yet more stable, and nobody had 1.7 source access. Even the other team members or developers.