HI

WinEQ 2.0 Pro discussion and support

Moderators: Lavish Software Team, Moderators

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Thu Feb 17, 2005 7:48 pm

No problem.

(Note: the in-game console is toggled by hitting the ` key by default. Read on)

To make the FPS indicator, add a hud element. This is done through the in-game console like so:
hudadd fps 0,0 ${FPS}
hudadd is the ocmmand, which takes 3 parameters.. name, location, and text. The ${FPS} thing gets parsed into the actual framerate. You can change it a little bit to say something like FPS: ${FPS} if you'd like, and you can put it in a different location by playing with the 0,0 part.

The FPS limiter in IS is set to 60 fps calculate (FPS limiter) for foreground, and 30 fps absolute (CPU limiter) for background. You can drop it down to 20 fps for background by entering this command in the in-game console:
maxfps -bg 20

These commands would have to be typed each time, BUT you can make a file called "AutoExec.ice" in your inner space folder, and put the commands there instead -- and that way they will automatically be used for every IS session. .ice files are just "command files" which store a series of commands, unlike scripts which require functions.

Finally, IS doesn't currently have a command-line option like WinEQ 2 did. I will definitely put this on my list, since IS aims to have every last feature of WinEQ 2. I'll put in a default key to toggle the FPS indicator as well, just like the memory indicator is done.

Anything else just ask :)

bob_the_builder
GamingTools Subscriber
Posts: 89
Joined: Sun Jul 11, 2004 2:08 pm

Post by bob_the_builder » Thu Feb 17, 2005 7:54 pm

Ok ... auto run shortcut like WINeq had .. last question and I'll leave you be , Lax !!!

Bob

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Thu Feb 17, 2005 8:30 pm

Woops I answered that as the "Finally" part but didn't make it clear that it's one and the same. It is now on my list. Thanks :)

Post Reply