Quote:
Originally Posted by ARGH
biggest issues;
1] propellar not visible due to stupid epilepsy rules. we need a visible prop. its an immersion-killer without it. if you cannot get around this then quietely release a backdoor fix so the end-user can enable it through config tweaks.
2] all this time i thought invisible tracers on spits was a bug. you should change the default loadout to have tracers so common players won't be confused.
3] you promised the rendering thread getting its own dedicated core and it will double fps. we really need this but have not heard anything since.
4] G940 flight stick not fully compatible with game, sticky fire button, throttle sensitivities not accurate, and what appears to be some input lag. i assume joystick issues spill to other FFB brands as well.
5] we need some form of tree / forest collisions. maybe you can insert invisible building meshes with physics enabled on top of the visible trees or something.
6] AA not working properly / not applied on every object.
7] allow default loadouts to be changed and some input settings do not appear to work. rear view camera on spit appears bugged as well.
|
Although I'm only an end user I can give you some answers mate:
1] Propeller IS visible indeed. It's as visible as in RL (we are used to props on movies and videos, which are substantially more visible than in RL)
2] There are no tracers on the Spitfire due to historical accuracy. If you want tracers, make a custom loadout on the loadout screen
3] As far as I know since early april all rendering work (i.e. loading textures, etc) is distributed between all the cores of your CPU (in a multicore CPU obviously)
4] I know nothing about the G940, so I can't be of any help here. Please note that FF has been activated in this patch though so not all is lost
5] IMHO tree collission is not the highest priority right now. Luthier team should focus on other most important things that are yet to be fixed
6] Yeah, you are right. AA doesn't work for me neither ATM
7] According to Luthier they are working right now on this. Im sure it will be fixed on the next beta patch
Cheers,
05-19-2011, 08:37 AM
Threaded Mode