Member
- Jun
- Threads
- 1
- 42
- 1
- 8
AD: Mt2009 - Mobile & PC - 30 January 2026 CHECK THE PRESENTATION!
Hey everyone,
I'm running into a very annoying client-side bug where a debug text (TempF1=1.000000, TempF2=1.000000, etc.) randomly appears on screen. MartySama 5.8
The main issues are:
The text seems to be triggered randomly during gameplay. This happens even though all debug modes in the Python source (e.g., in game.py) are completely disabled.When the text is visible, the numpad * key toggles between this "TempF" text and the regular FPS display, but the overlay cannot be turned off completely.We believe this issue started after we implemented Owsap's Multi-Language System. It seems possible that some part of that system is writing to the debug buffer under specific, random conditions.Has anyone encountered a similar issue, perhaps with this specific system? Any pointers on where to look in the source would be greatly appreciated, as a search for the "TempF" string has not been successful so far.
Thanks in advance!
I'm running into a very annoying client-side bug where a debug text (TempF1=1.000000, TempF2=1.000000, etc.) randomly appears on screen. MartySama 5.8
To see the download links,
Log in or register now.
The main issues are:
The text seems to be triggered randomly during gameplay. This happens even though all debug modes in the Python source (e.g., in game.py) are completely disabled.When the text is visible, the numpad * key toggles between this "TempF" text and the regular FPS display, but the overlay cannot be turned off completely.We believe this issue started after we implemented Owsap's Multi-Language System. It seems possible that some part of that system is writing to the debug buffer under specific, random conditions.Has anyone encountered a similar issue, perhaps with this specific system? Any pointers on where to look in the source would be greatly appreciated, as a search for the "TempF" string has not been successful so far.
Thanks in advance!
