![]() |
|
#1
|
|||
|
|||
![]()
I already have a question:
To dev team regarding the SpeedTree technology. We all know the problems with them: shimmering, LOD changes and what not. I scoured thru SpeedTree forums and saw similar issues with trees and also solutions. Add that there are new versions of it etc. So my question is that has dev team worked with SpeedTree Inc and using newer version and tools? Can anything be done with trees? Ок? |
#2
|
||||
|
||||
![]() Quote:
__________________
![]() Gigabyte X58A-UD5 | Intel i7 930 | Corsair H70 | ATI 5970 | 6GB Kingston DDR3 | Intel 160GB G2 | Win 7 Ultimate 64 Bit |
MONITOR: Acer S243HL. CASE: Thermaltake LEVEL 10. INPUTS: KG13 Warthog, Saitek Pedals, Track IR 4. |
#3
|
|||
|
|||
![]()
Or if FMs have been addressed in an earlier question then perhaps:
Have you considered a formal bug tracking system that the community can get involved in? It is difficult to tell what bugs the devs are/are not aware of at the moment since the bug threads do not get feedback. |
#4
|
|||
|
|||
![]() Quote:
Errors FM - separate conversation, not for this format. |
#5
|
||||
|
||||
![]()
Yeah, that would be very useful.
__________________
![]() ![]() i7 7700K 4.8GHz, 32GB Ram 3GHz, MSI GTX 1070 8GB, 27' 1920x1080, W10/64, TrackIR 4Pro, G940 Cliffs of Dover Bugtracker site: share and vote issues here |
#6
|
|||
|
|||
![]()
Now this is the most important question of all. Please put that on #1 in the list. A read only "known bugs" list would be enough so we can see which bugs are already reported and worked on.
|
#7
|
||||
|
||||
![]() Quote:
A current list of errors maybe similar in its effects, but there is no feedback either. I remember, formerly ran Insuber's list, the "Priority Bugs & Other issues need to be hurt look into", but it is no longer "sticky" (last update 4. Jun ![]()
__________________
![]() ![]() i7 7700K 4.8GHz, 32GB Ram 3GHz, MSI GTX 1070 8GB, 27' 1920x1080, W10/64, TrackIR 4Pro, G940 Cliffs of Dover Bugtracker site: share and vote issues here |
#8
|
|||
|
|||
![]() Quote:
Quote:
|
#9
|
|||
|
|||
![]()
Blacksix.....ask him is there a chance to recruit "open beta testers" out of community members from this forium? More testers more bugs noticed....khm
|
#10
|
|||
|
|||
![]()
We prepare 5 screenshots with damage model)
Quote:
Why, if we publish the beta patches of open access? |
![]() |
|
|