Quote:
Originally Posted by David Hayward
The sort of programming I do is absolutely nothing like programming a game, that's why I never even considered offering solutions to Luthier. It's also why I'm only using generalities.
You said that you have minimal programming knowledge. Where do you get the nerve to criticize something when you have virtually no experience of your own?
|
Quote:
Originally Posted by David Hayward
If no calculations have to be made until an impact occurs, how does the computer determine that an impact has occurred? Magic?
|
You are a complete moron. Try reading the posts. Oh, I forgot you dont have the intellectual capacity to type more than 2-3 sentences in a row.
I should not even answer your idiotic question, the issue is and has never been the collision itself - its the calculations for working out the collision that is the problem, because currently they are not selectivly generating hit boxes based on distance as every other sane programmer would have the engine do (based on what we have been told).
Also I didnt just beta test, I know a number of devs from games pretty well and have talked to them about similar issues.
No point in arguing with you, seriously the biggest fanboy on the forum, when ever someone criticises the game in any way you are always there to spout ignorrant crap. If I am so unqualified (and indeed I am not to programme the engine) then why did they mention implementing my suggestions specifically about 3-4 months after I posted/started advocating for them? Why did luthier do a complete 180 on dx11 uses?
Better than your track record.