Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
1.4.0 and GIT version cutoff??
#1
I was wondering what was the latest GIT version that made it into the stable 1.4.0 version. Was the 1.3.1-1623 GIT version the last one or what?
OS: Windows 10 Pro (64 bit)
CPU: Intel i5-8400 2.8 GHz (4.0 GHz Turbo)
GPU: Gigabyte GeForce RTX 2060 Gaming OC (6 GB)
RAM: Ripjaws V Series, 2x8 GB DDR4 (2666 MHz)
Motherboard: GIGABYTE B360M D3H
Power supply: EVGA SuperNOVA G3 550 W
Reply

Sponsored links

#2
The build bot is just naming the builds incorrectly, they are actually the 1.5.0 builds on there
[Image: ref_sig_anim.gif]
Like our Facebook Page and visit our Facebook Group!
Reply
#3
(01-24-2016, 12:58 AM)refraction Wrote: The build bot is just naming the builds incorrectly, they are actually the 1.5.0 builds on there

I believe the OP is asking which 1.3.1 build was used as the release candidate.
[Image: gmYzFII.png]
[Image: dvedn3-5.png]
Reply
#4
(01-24-2016, 01:23 AM)Nobbs66 Wrote: I believe the OP is asking which 1.3.1 build was used as the release candidate.

Yeah like which GIT version was the last one to be included in the stable release. Basically like after which GIT version did you guys stop and say "okay this is everything we're gonna included in the stable release before releasing it"...
OS: Windows 10 Pro (64 bit)
CPU: Intel i5-8400 2.8 GHz (4.0 GHz Turbo)
GPU: Gigabyte GeForce RTX 2060 Gaming OC (6 GB)
RAM: Ripjaws V Series, 2x8 GB DDR4 (2666 MHz)
Motherboard: GIGABYTE B360M D3H
Power supply: EVGA SuperNOVA G3 550 W
Reply
#5
Any build after jan 5th is not present though seeing that is when it was compiled

v1.5.0-dev-63-g3c528f0 probably based off this seeing there was only 2 build that day and stable is was complied later in the day
Reply
#6
We might have fu**ed up with the tags. We already had this issue with 1.2/1.3 where we had to add a new version/tag 1.3.1 to sync with the build bot.

Can anyone define the issue exactly?
[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
#7
(01-24-2016, 12:58 AM)refraction Wrote: The build bot is just naming the builds incorrectly, they are actually the 1.5.0 builds on there

It doesn't look to me like it's naming them incorrectly now. The 1.4 release is not on the build bot AFAIK since it was built from a non-master branch.
[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
#8
(01-24-2016, 03:55 PM)avih Wrote: It doesn't look to me like it's naming them incorrectly now. The 1.4 release is not on the build bot AFAIK since it was built from a non-master branch.

Oh okay yeah I've noticed that gregory has been hard at work on the GIT versions recently.  I was wondering if it would be better to still use DX11 or OPENGL on that stable version. I don't know exactly what features made it into the stable version. Idk I like to have the latest features so I might just stay with the developmental versions if it's not that big of a difference right now
OS: Windows 10 Pro (64 bit)
CPU: Intel i5-8400 2.8 GHz (4.0 GHz Turbo)
GPU: Gigabyte GeForce RTX 2060 Gaming OC (6 GB)
RAM: Ripjaws V Series, 2x8 GB DDR4 (2666 MHz)
Motherboard: GIGABYTE B360M D3H
Power supply: EVGA SuperNOVA G3 550 W
Reply
#9
So far, git has only a faster blending accurate algo + a new hack to acclerate it in some specific game (xenosaga, zone of enders)
Reply
#10
(01-24-2016, 09:42 PM)gregory Wrote: So far, git has only a faster blending accurate algo + a new hack to acclerate it in some specific game (xenosaga, zone of enders)

Okay so would you recommend me to stay on DX11 for the new stable release?
OS: Windows 10 Pro (64 bit)
CPU: Intel i5-8400 2.8 GHz (4.0 GHz Turbo)
GPU: Gigabyte GeForce RTX 2060 Gaming OC (6 GB)
RAM: Ripjaws V Series, 2x8 GB DDR4 (2666 MHz)
Motherboard: GIGABYTE B360M D3H
Power supply: EVGA SuperNOVA G3 550 W
Reply




Users browsing this thread: 1 Guest(s)