For larger models we tend to use the POD format (as seen in IntroducingPOD and others), but we’ve also done the same kind of thing as you describe before. It should take a bit longer to compile, but I’ve never seen compile times this excessive.
I assume you’re using a fairly modern PC to build this? The current release of our SDK is version 2.6 and you appear to be using a 2.3 release from a year and a half ago - I would recommend retrieving the new version and using this. It probably won’t affect compile time much, but you’ll benefit from any bug fixes we’ve incorporated since then and it may be that a setting in your project is causing the long compile times and a fresh project might correct that.
Otherwise you may want to consider checking your system in other ways: did you have a virus scan running, possibly re-installing visual studio etc.
If you’re still having trouble then at least putting your data into a separate source file should mean it only needs to be compiled once and that should save some time.
Thank you for your quick feedback, Gordon.
It may be that you have built application against diffrent version of pcemulation than the one you are using to run this application against. Â Can you just run any demo/traning course from SDK (binary, without building) by coping libraries of pcemulation into direcotry of that application? When you use VC2008 for building and running application then you can see in output what libraries are being loaded, so please make sure that these are the same libraries as the one used for linking. Tell us if it helps
This method works after I copied the following files
Also, I found to build my project using this new version OGLES2_WINDOWS_PCEMULATION_2.06.26.0649 is much slower than using the old version 2.0.3, which is really not what I expected. I really regret I removed the old version. I am wondering, do you still have the OGLES2_WINDOWS_PCEMULATION_2.03.23.1162 some where? I prefer the old version than this one.
It is very odd that this new version has gone much slower. Could you describe whether this happens in all occasions or only when you use specific features and how many polygons, textures, etc. you use in your example (and also you HW acceleration). We will try to reproduce this problem.
We do not recommend going back to an older version as there has been many fixes since 2.3 and we will not be able to support you if you use an old emulator.