Very Slow now
Blitz3D Forums/Blitz3D Beginners Area/Very Slow now
| ||
| I just re-installed Blitz2D and updated to the latest patch and now it seems My code all runs Very slow? Any ideas what the problem is. (Or is it Directx 9 as I had Directx 8 before as far as I remember) Any ideas? Mike R |
| ||
| If you are using a Nvidia card, you likely need to downgrade your drivers. |
| ||
| Or stop using the "Text" command. I had to rewrite parts of my game over the weekend to use bitmap fonts instead of the internal "text" command because of this issue ... |
| ||
| Also, the slowness might be due to the debug feature being On. |
| ||
| I do have an nvidia card. Whats the issue with the drivers? |
| ||
| Whats the issue with the drivers Nvidia doesn't know how to write drivers that work properly. There are some threads about them in the "bug reports" forums... |
| ||
| I have an Nvidia card, and it flies like the wind. Maybe there are variations within the NVidia card family drivers... |
| ||
| Yes, there are screedsa and screeds of different drivers; new ones come out all the time. It's only the latest drivers that have a problem, and apparently the next ones will be fixed again. |
| ||
| I am glad to read this thread cos I got the latest Nvidia drivers (like a good person) and my display went South. Or West. Anyway, it needs fixing. I have to deal with this compulsion to UPDATE DRIVERS, when everything is working fine as it is :) |
| ||
| 43.51 still has the same problem. Have reverted back to the 30.xx drivers for now. Hope it DOES get fixed. Mike |
| ||
| I use 41.09 and have no probs... usually newer is better but in Nvidias case it is not nearly always so - and it has been like that a long time... and latest drivers (or two) were *exceptionally* buggy! ...Instead of trying to release a new set every week they really should concentrate more "quality over quantity"... |
| ||
| I think that the proggers (i.e. programmers) writing the drivers are probably in a haste and hurry to get it over with. Problem with that, is, of course, that like the old maxim: "haste makes waste." No, really, it does! A good rule of programming is to change only one thing at a time, that way, if something goes wrong, you know where it crept in. In their hurry to fix one thing, they probably overlook the effect their change will have on a part of the program elsewhere, and in haste, don't test it well enough. But, hey, what do I know? Maybe they are conscientious and take their time, and Murphy's Law ("If anything can go wrong, it will.") just kicks in anyway! |
   |