Fire 2.0 xTreme
2 posters
Page 1 of 1
Fire 2.0 xTreme
Fire 2.0 xTreme x64 PP
[You must be registered and logged in to see this link.]
Fire 2.0 xTreme w32 NS
[You must be registered and logged in to see this link.]
Fire 2.0 xTreme w32 no SSE2 NS
[You must be registered and logged in to see this link.]
Fire 2.0 xTreme source code
[You must be registered and logged in to see this link.]
[You must be registered and logged in to see this link.]
Fire 2.0 xTreme w32 NS
[You must be registered and logged in to see this link.]
Fire 2.0 xTreme w32 no SSE2 NS
[You must be registered and logged in to see this link.]
Fire 2.0 xTreme source code
[You must be registered and logged in to see this link.]
guest51- Posts : 5
Join date : 2011-06-14
Re: Fire 2.0 xTreme
certainly recommend that users of previous versions now use 2.0.
any fire.cfg file or saved UCI option from a previous version should be 100% compatible with 2.0
there likely no big ELO increase, but perhaps a small one, and several major issues
have been resolved, largest of which was the occasional Playchess.com crashing.
major changes:
now supports up to 64 cores/threads
occasional crash fixed
code improvements, bitwise optimizations
SEE piece/capture values are no longer constant entities
fire.cfg incorrect default value for Prune_Pawn fixed: Prune_pawn = 160
Fire now recognizes whether or not the system supports hardware popcount
and/or large pages, and self-configures itself accordingly
some code cleanup, formatting, and re-organization
more complete Log implementation
UCI clear hash button added
etc.
at the moment this is about as good as I can get it...
thanks for welcoming me on your great forum!
best begards,
Norm (kranium)
any fire.cfg file or saved UCI option from a previous version should be 100% compatible with 2.0
there likely no big ELO increase, but perhaps a small one, and several major issues
have been resolved, largest of which was the occasional Playchess.com crashing.
major changes:
now supports up to 64 cores/threads
occasional crash fixed
code improvements, bitwise optimizations
SEE piece/capture values are no longer constant entities
fire.cfg incorrect default value for Prune_Pawn fixed: Prune_pawn = 160
Fire now recognizes whether or not the system supports hardware popcount
and/or large pages, and self-configures itself accordingly
some code cleanup, formatting, and re-organization
more complete Log implementation
UCI clear hash button added
etc.
at the moment this is about as good as I can get it...
thanks for welcoming me on your great forum!
best begards,
Norm (kranium)
guest51- Posts : 5
Join date : 2011-06-14
Re: Fire 2.0 xTreme
Thanx buddy,
Terminator-I- Moderator
- Posts : 193
Join date : 2011-05-11
Location : Dubai
Similar topics
» Fire 2.2b xTreme GH x64
» Fire 2.2a xTreme GH x64
» Fire 1.5 xTreme
» Fire 2.1 xTreme
» Fire 2.2 xTreme
» Fire 2.2a xTreme GH x64
» Fire 1.5 xTreme
» Fire 2.1 xTreme
» Fire 2.2 xTreme
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum