it worked i just had to restart my computer
Your welcome and have a nice day.
oh nvm i closed it and opend it and now i get the same error again
- Intel Core i5-2430 @ 2.40 Ghz
- 8 GB ram
- Windows 7 64-bit
- 1366x768
I cannot select anything with LMB. I ran in several times with no issues besides that, but got it to crash today when I zoomed iin and then tried zooming out through the tree.
Also, I see some faces overlapping on the models of the rabbit and human.
Faulting application name: Stonehearth.exe, version: 0.1.0.43, time stamp: 0x52866a6a
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1116
Exception code: 0x80000003
Fault offset: 0x00013219
Faulting process id: 0x1164
Faulting application start time: 0x01cee498fbc701b9
Faulting application path: C:\Program Files (x86)\Stonehearth\Stonehearth.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 96bbf363-508c-11e3-84f3-101f746a1d23
Details
- Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2013-11-18T20:04:11.000000000Z
EventRecordID 114961
Channel Application
Computer Jonathan-HP
Security
- EventData
Stonehearth.exe
0.1.0.43
52866a6a
KERNELBASE.dll
6.1.7601.18229
51fb1116
80000003
00013219
1164
01cee498fbc701b9
C:\Program Files (x86)\Stonehearth\Stonehearth.exe
C:\Windows\syswow64\KERNELBASE.dll
96bbf363-508c-11e3-84f3-101f746a1d23
1 Like
@LordNevs Firstly, please try to avoid the double-posting, as it both irks quite a few of the more OCD-ish forumgoers (myself included), and it tends to call the moderators into action⌠and @Geoffers747 (while he hasnât been very active recently) has a bit of a⌠short list⌠which he tends to keep updated with⌠targetsâŚ
With that in mind, try running it as an Administrator instead of a normal user. That jumped my FPS up from around 30 fullscreen to over 200 fullscreen (for some reason). Also, the goals are for OSX, not iOS. Big difference between the two, and we wouldnât want anyone to get too confused.
3 Likes
thanks @ManOfRet ⌠and while my list isnât quite as short, Iâm far more hostile with those who become its residents⌠
2 Likes
As others have mentioned, your models seem to have quite a bit of âZ-Fightingâ on their joints.
I would upload an image but it seems I am new and cannot do so.
1 Like
That sucks and Iâm sure if you ask someone else for help they can help you.
Done some first testing, normal usage only so far (not tried my worst yet though).
Only some graphical issues so far, texture/shadow/dots/lines. See video below for details.
Tried both windowed 1280x720 and maxed window on my 1080p screen (but not âfull screenâ since there is no option for it). FPS are around 200-250 and 130-150 in those two modes. Frapsed it in 60 fps with no issues.
Computer Specs:
Mobo: ASUS P8Z68-V/GEN3 Socket LGA1155
CPU: Intel Core i5 2500K / 3.3 GHz
RAM: Corsair XMS3 16 GB 1600 MHz DDR3 (CMX8GX3M2B1600C9)
GFX: Sapphire Radeon HD6850 1GB GDDR5 PCI-E
HDD: Samsung SSD 830 Series 256GB 2.5" SATA3.0
Software:
Windows 8 Pro
Graphics Driver v. 9.012-121219a-152192C-ATI
Not 100% sure it is the latest for this old board, but I update whenever it says I shouldâŚ
1 Like
And Iâve now tried it on my desktop computer.
Specs:
- i5-4670 3.4 GHz
- EVGA GTX 680
- 16G GB 1600 MHz RAM
- 2x 1 TB 7200 HDD
I get ~500 FPS and I had NO problems what so ever. The only thing that I thought was a bit weird was, that it takes 57% of my CPU capacity. I think that is quite odd considering my CPU, but I hope you can fix it.
Is tom gonna release, an like ââfixed/updatedââ version of the graphic test, because i think we pretty much discovered and reported all the bugs now.
I donât know for sure but typically such tests are used to identify issues and the findings will go into the final product. The devs might focus more on getting the fixes implemented in the first, playable release than in releasing another version of the Graphics Test Program.
Update: As it seems Stonehearth proofs me wrong and we can expect another version of the Graphics Test.
3 Likes
thanks for the report⌠this has indeed been mentioned before, and is simply due to the fact that no optimizations or performance tuning is in place yetâŚ
as @voxel_pirate mentioned, this is unlikelyâŚ
1 Like
No show stopping issues here but I would also like to report the flickering yellow pixels on selected items and (what appears to be) z-fighting, especially on the hands of the people and the sides of the rabbitâs faces. Iâm using a 560ti. I upgraded drivers from 311.06 to 331.65 with no noticeable difference.
it seems that when i restart my computer i can play it but when i close it and relaunch i get the read pending error so i restart my pc again and again i can play it but after that same error
1 Like
Just wanted to let you all know that weâre busily working on fixes to a number of the bugs youâve reported. To help organize the information, @SteveAdamo and I have put together a bug report category here on the discourse:
http://discourse.stonehearth.net/category/support/bug-reports
The bugs currently in the category are inspired by the major issues in this thread. Feel free to add any details youâd likeâespecially system and reproduction info.
A bug-writing and category use guideline can be found here:
Let us know how the system works for you; weâd like to get whatever kinks out before the preview release. 
3 Likes
Got the error == GL_NO_ERROR as soon as I started the program
Attempts to update components (just SFML so far) manually resulted in âThe Application failed to start correctly (error code 0xc000007b)â - further steps performed with original installation
Attempts to run program on alternate hard drive in standard %ProgramFiles% dir had no effect
Attempts to run as administrator had no effect. Will attempt with other Compatibility settings later tonight
Graphics drivers have not been updated in some time, will attempt later tonight
CPU - quad 3.5 GHz (AMD Phenom II X4 970)
Memory - 10 GB (9.75 âAvailableâ)
OS - Windows 7 Home Premium, 64-Bit (currently running with heavy modifications to the base user directories)
Graphics - ATI Raeon HD 5700 Series
Screen Resolution - 1 monitor at 1366 x 768 (using DVI to VGA converter)
Application Logs:
Faulting application name: Stonehearth.exe, version: 0.1.0.43, time stamp: 0x52866a6a
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1116
Exception code: 0x80000003
Fault offset: 0x00013219
Faulting process id: 0xfec
Faulting application start time: 0x01cee55963deb27a
Faulting application path: D:\Program Files (x86)\Stonehearth\Stonehearth.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: a223497c-514c-11e3-b414-485b39d00b75
indeed! feedback on how to improve the process is certainly welcomeâŚ
iâm thinking that we may want to have updated thread titles to correspond with the current state of a given bug, so:
Bug : title goes here
Bug [Confirmed] : title goes here
Bug [Acknowledged] : title goes here
Bug [Resolved] : title goes here
Bug [Not a bug] : title goes here
etc.
2 Likes
Sure! Though could you clarify the difference between confirmed and acknowledged?
iâve typically used that to differentiate when a user [confirms], which here we could replace with the like function, and the developer [acknowledges] the bug⌠im good either way⌠