Hmmm...That does make sense. Part of the problem here is that Visual
Basic 6, the language a lot of accessible games are written in, was
released in 1998 before the Windows unicode standard was a core part
of the Windows operating system and Windows API. Unicode support on
Windows really wasn't fully standardized until Windows XP was released
in 2001 which obviously made languages like Visual Basic 6 obsolete
unless the developer in question intentionally created his or her
software using unicode support. Future versions of Visual Basic like
Visual Basic .Net, which was released in 2002, resolved a lot of
problems inherent in Visual Basic 6 and earlier, but as you can see
several game developers here haven't adopted Visual basic .Net and
still are using Visual Basic 6 even though it is far passed its prime.
On 6/23/10, Phil Vlasak <p...@pcsgames.net> wrote:
> Hi Thomas,
> The same error occurs with the GMA engine in that it uses the ASCII codes
> instead of Unicode.
> The divide by 0 error happens as the math function codes have also changed.
> David is working on re-writing the math functions in Unicode and has been
> successful so far in a beta of the new engine.
Gamers mailing list __ Gamers@audyssey.org
If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org.
You can make changes or update your subscription via the web, at
All messages are archived and can be searched and read at
If you have any questions or concerns regarding the management of the list,
please send E-mail to gamers-ow...@audyssey.org.