Elysian Shadows

Wow so in the new version of my engine I have completely phased out immediate mode and replaced it with retained mode
and my CPU usage is consistently 1% or lower. As opposed to immediate mode which ran at 6% CPU usage and up to 25% ( no frame limit ).
Also keep in mind that when I tested immediate mode It was frame limited to 50 FPS and testing retained mode I simply delay for 1 millisecond. Even if I remove that 1 ms delay it STILL only uses 20% that's consistently 5% better than immediate mode.
Also when I asked the question earlier about rendering 2500 textures to the screen, the FPS pre-DMA was 370 and post-DMA is 200
so I AM sacrificing 170 FPS but it's a lot more easy to use.
Well I am thoroughly exited about my new engine, which by the way is being built from scratch ( again ).
But I am taking my time with this version and I'm glad because it's VASTLY superior to the previous version(s).
Anyway that's sort of a status update for those who care to have it.

Just keep in mind, CPU usage as reported by Task Manager or similar is not at all a valid performance benchmark. If you ever need to seriously analyze your application you should definitely consider looking into a code profiling or memory profiling suite. There are at least a few decent ones for Visual Studio that you can download free.

Oh. .
Well is fraps good for FPS benchmarking?

'The program can't start because MSVCR90.dll is missing from your computer. Try reinstalling the program to fix this problem.'

I can't make a game if Visual Express won't let me run it.
Does anyone know how to fix this?
And before you ask I've reinstalled visual express, and 4 versions of the vcredist... and I also ran a virus scan.

That is bizarre. As a quick fix, before someone with MSVC knowledge can help you, you can manually put the .dll on the same directory you run the program.

Oh that's even better:
'Runtime Error! R6034 An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information.'
And then:
'The application was unable to start correctly (0xc0000142). Click OK to close the application.'
Now you may say "Why don't you just build for release?" well I have a bug that I can't trace back to it's source because release doesn't have reliable breakpoints.

Does this help?

http://msdn.microsoft.com/en-us/library ... 80%29.aspx

No but I figured it out on a related page.
Here's how to fix it:
Got to C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\redist\Debug_NonRedist\x86\Microsoft.VC90.DebugCRT
(or wherever you installed you vcredist)
Copy the file 'MSVCR90d.dll' to your application directory.
Rename it to 'MSVCR90.dll'

Although it still doesn't work properly.
F*ck it I'm gonna format my hard drive and re-install windows.

RandomDever wrote:F*ck it I'm gonna format my hard drive and re-install windows install linux.

I corrected it for you.

bbguimaraes wrote:

RandomDever wrote:F*ck it I'm gonna format my hard drive and re-install windows install linux.

I corrected it for you.

Yeah.. somehow I don't see that fixing his Visual Studio problem very well.

While you are trying to figure out how to solve it, you can link to MVSC90 statically.