Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Where can i find "nightly" PCSX2 updates?
#1
Brick 
For compiling. I'm not a programmer, but https://github.com/PCSX2/pcsx2 not like the right place -

[Image: ImWWu0T.jpg]
Reply

Sponsored links

#2
That's just github repo.

Go here: http://buildbot.orphis.net/pcsx2
[Image: gmYzFII.png]
[Image: dvedn3-5.png]
Reply
#3
(12-20-2017, 04:30 AM)Nobbs66 Wrote: Go here: http://buildbot.orphis.net/pcsx2

Does not look like "nightly" builds, or I do not understand something? -

[Image: e6dboPl.jpg]
Reply
#4
"Nightly" is just the term used to describe the builds because they're generally regarded as "unstable, development builds" (ours are fine, you won't see any major stability issues)

The date you see above is just the most recent work that's been done.
Reply
#5
Yeah the buildbot doesn't work again it seems. So far it's 1 commit behind which isn't such a huge deal, unless you're playing Tekken 5 that is. Still nothing major tho.
CPU: I3-4160 3.6GHZ
Motherboard: Asrock B85M - DGS
RAM: Hyper X Savage 2x8GB 1.6GHZ cl9
GPU: Asus AMD Radeon R7 360 OC 2GB GDDR5
OS: Windows 7 Ultimate SP1 64bit
Reply
#6
(12-20-2017, 05:10 AM)lightningterror Wrote: Yeah the buildbot doesn't work again it seems. So far it's 1 commit behind which isn't such a huge deal, unless you're playing Tekken 5 that is. Still nothing major tho.

There may be forks of the project? A commit for the last 16 days is not looks like a great development project, as it looks from the outside.
Reply
#7
Well the project is pretty far along. Finding fixes for everything isn't exactly as easy as it used to be.

There's alot of work that goes on in the background that you may not think about/see. Smile
Reply
#8
The date mentioned there is the date when the merged commit was created, not the date when it was merged to master branch. Look at it carefully, first build has a date of 11/24 and the second one is having 12/10.

To be honest, I'd prefer to have the merged date there instead.
We're supposed to be working as a team, if we aren't helping and suggesting things to each other, we aren't working as a team.
- Refraction
Reply
#9
(12-20-2017, 06:38 AM)ssakash Wrote: To be honest, I'd prefer to have the merged date there instead.

Generally that's nicer, but this requires us to ask the author to rebase onto latest master and make sure the patch is still valid (or rebase and merge via the github UI, which puts the responsibility on the correctness of the rebase to whoever rebased+merged it).
[i7-3630qm/gt650m-2G/Win-7] [i7-4500u/R.HD8850m/Win-8.1] [2010-MBA/OSX-10.9.x]. Scroll smoothly with SmoothWheel for Firefox.
Reply
#10
That sounds like extra work, it's okay atm since latest merge is still on top of the list.
CPU: I3-4160 3.6GHZ
Motherboard: Asrock B85M - DGS
RAM: Hyper X Savage 2x8GB 1.6GHZ cl9
GPU: Asus AMD Radeon R7 360 OC 2GB GDDR5
OS: Windows 7 Ultimate SP1 64bit
Reply




Users browsing this thread: 1 Guest(s)