Just a note ... Recordings I make with iShowU are studdering since maybe two or three render test versions, no matter if Engine is started directly or through Editor. In 2.5b8 and before it was fluent, maybe even in the first 2.5b9, so there must be something you changed. The FPS of the game are not influenced by iShowU running or not. The gameplay becomes studdery and jerky as soon as iShowU is running.
Makes it impossible to record proper movies.
On another note you must have done something right with memory management. Engine/Editor quit way faster and don't block the computer afterwards anymore - in the past Finder took ages to become responsive again and Firefox took bloody ages.
If you experience jerkiness in the screen as though you have low fps when you don't, it means not enough of your CPU is being devoted to the game. Brian's changes probably use more CPU up. Screen recording takes a lot out of the CPU. Lower iShowU's recording resolution/quality.
(2008.10.02 09:32 PM)teh1ghool Wrote: [ -> ]If you experience jerkiness in the screen as though you have low fps when you don't, it means not enough of your CPU is being devoted to the game. Brian's changes probably use more CPU up. Screen recording takes a lot out of the CPU. Lower iShowU's recording resolution/quality.
Right now, the new physics (still a work in progress) are all ray traced and take a LOT of time. This is my first hot spot for optimization, and I've already knocked a lot off that (and there will be more coming, especially in the next beta.) Second is some lighting code, and third is getting the obscuring working right so that can be used as a general speed up.
As you've seen, I've done a good job of reducing the memory footprint of dim3 (especially engine and editor.) I can go a bit farther, but I got a good chunk reduced and that's what's helping you out.
Now that Editor and Animator are almost out of the way, I can get back to Engine full time and get that in working order.
[>] Brian
As I said the jerkiness is there with even iShowU just running, not recording.
(2008.10.02 09:32 PM)teh1ghool Wrote: [ -> ]If you experience jerkiness in the screen as though you have low fps when you don't, it means not enough of your CPU is being devoted to the game. Brian's changes probably use more CPU up. Screen recording takes a lot out of the CPU. Lower iShowU's recording resolution/quality.
Check activity monitor and see what's eating your cpu.
Well nothing is eating up my CPU, both cores are <10% recording or not, what do you think I'm stupid? No difference if iShowU is set to 1280x720 or 16x16. FPS is at a constant 73-77 FPS. I'm saying there are more or less heavy jerks during play, wherever it comes from - memory, soundflower, refresh rates, ishowu, raining outside ...
(2008.10.03 04:09 PM)Bradamante Wrote: [ -> ]Well nothing is eating up my CPU, both cores are <10% recording or not, what do you think I'm stupid? No difference if iShowU is set to 1280x720 or 16x16. FPS is at a constant 73-77 FPS. I'm saying there are more or less heavy jerks during play, wherever it comes from - memory, soundflower, refresh rates, ishowu, raining outside ...
What speed is your hard disk? Also how much RAM is being filled?
If its a laptop then i guess it has a 4200 RMP disk which if the program is writing to the disk as its recording could be causing the jerkin. Otherwise the RAM could be full and its forcing the system to start swapping virtual memory.
And finally, make sure you have lots of free disk space before you start as OSX needs in excess of 1Gb free on the disk to throw the vm cache. (then add to that the uncompressed video your recording)
Next version, things are moving right along:
http://homepage.mac.com/ggadwa/Misc/MeshOnlyTest.zip
There's more Animator/Editor fixes, there's the new (yes, this will cause a fight) text rendering engine, a bunch of optimizations (hopefully I haven't broken anything), some physics updates, bug fixes, and a couple requests.
This version will (hopefully) mark where I move onto working on engine mostly (physics and networking are the two big ones.)
Code:
Editor
* if any axis = 0 when making a mesh grid, remove that axis
* better support for replacing multiple meshes over other multiple meshes
* fixed bug where new meshes could have odd message settings
* some minor fixes to map auto-generator
* raise/lower mesh menu items now work
Animator
* animator would allow non-UVs to be loaded instead of erroring out
* import errors could sometimes leave model in indeterminate state
* importer deals with rouge vertexes better and auto-deletes unconnected vertexes
* better importing for OBJs with very tiny scales
* normal import works better
* recalculate normals works better
Engine
* a number of lighting optimizations
* changed the way it generates mipmaps, removed unnecessary "on card" option
* when going into GUI modes with the view in the background, save screenshot, mask, and display instead of redrawing view (slow)
* text now created in engine
+ text has better anti-aliasing
+ text has better proportional spacing
+ set in interface.xml with <font name="Arial" alt_name="Courier" />
+ drawing large amounts of text is a bit faster
* better default bump values
* fixed a bug where flying wouldn't take Y input
* fixed a bug where hilited meshes would draw black
* map open progress bar wasn't very balanced
* physics changes
* improved steps physics
* improved ramp physics
* fixed bug with standing on moving platform physics
Scripting
* added to events:
+ xxx.event.setMessageData(index,data); // index is 0..7, data is a variable of int, float, boolean, or string
+ var v=xxx.event.getMessageData(index);
* added to objects:
+ obj.turnSpeed.topDownAngleOffset (offset for top down keyboard angles)
Don't worry about reporting any physics bugs to me, I know them all
Any other bugs are welcome!
[>] Brian
I downloaded that latest one but there wasn't any map in it!