NVIDIA and ATI

-
Few day ago I bought netbook with ATI Radeon graphic card. Before I always used cards from Nvidia and Intel. After day of installing tools to programming and profiling I ran for test L.B.A. Remake. And of course it didn't work. But after removing CUDA support that I needed to my thesis work, it started without problems.

But when app started i saw other problem: There were some weird stuff on my screen, they didn't look like they should. After two days of searching reason behind it I found that:

  • Nvidia allow more then it should. - I had invalid code (I probably write it very late in night because it was so stupid and when I saw it I thought how I could wrote it :] ). Code for each type of input to shaders (position, normals, texcoord0, ...) set glBufferData with size of all inputs and data set to NULL. On NVIDIA worked fine on ATI not.
  • NVIDIA and ATI have different bindings of Inputs - POSITION is always ATTR0 but other not. On end I decided on using in shaders defines with ATTRi that I bind for each type. I think that this will be safest and most efficient way.
  • Default value of input data -  if there is no binded input NVIDIA set input COLOR0 values on (1,1,1,1) but ATI use value (0,0,0,0).
There are probably other difference in them but right now I didn't found in working of program. If I find any then I share them.

On the end of work yesterday I was happy that I finally get hand on ATI card. Thanks to that I found some stupid code and for now I have hope that game will run on most of the graphics cards.

Comments

Post a Comment

Popular posts from this blog

Query commands execution

-
So like always start with problem description: I have some pool of command represented as enumerator. Each of command can have unique data that size can be different. I wanted to create system that allow me in easy way iterate over them and execute.  After some time I created this implementation: template<ECommands::enum cmd> bool execCommandTemp(ECommands::ENUM a_cmd, void* a_data) { if (a_cmd == cmd) { SCommand<cmd>::execute((SCommand ::SData*)a_data); return false; } return execCommandTemp<(ECommands::ENUM)(cmd+1)>(a_cmd, a_data); } template<> bool execCommandTemp<ECommands::WRAP>(ECommands::ENUM a_cmd, void* a_data) { return true; } bool execCommand( ECommands::ENUM a_cmd, void* a_data ) { return execCommandTemp<(ECommands::ENUM)0>(a_cmd, a_data); } where SCommand look in example such a way: template <> st...
Read More »

W.U. 0x20

-
Image
And as I said last time new preview is available: As you can see a lot has changed. Right now I mostly focus on gameplay so I do test of AI (some of them you can see on end of movie), changes in fight, items managing, fix some problem with physics and many other things. To say truth I don't remember them all :P So I'm going back to work and till next week.
Read More »

Few words about remake

-
Image
Time is something funny we don't notice when but it pass by so quickly. Few months ago I announced release of this pre-alpha build. Then it was so far away right now only a little bit more then month left. You probably wondering what changed in this time. So below you will find some summary of biggest changes (from my point of view): Component base architecture  Decision on big changes in engine architecture aren't easy. I think that transition from class base approach which looked like that : class CGameObject class CModelObject : public CGameObject class CPuppetObject : public CModelObject class CChcaracterObject: public CPuppetObject  to component base ( like in Unity 3D ) was one of the biggest and most problematic changes that I done in White Rabbit Engine in last years. I needed to change a lot of code, don't break the game that I have and in the same time change my approach to resolving problems.  Level Editor : New com...
Read More »