Disqus - Latest Comments for elenzil

Re: How to fix: MediaKit reports not enough space on device for requested operation

elenzil — Wed, 21 Mar 2018 12:03:59 -0000

great post, thanks. i had the exact situation with a WD Elements 4TB.
boy, 23 years of using *nix and i've never seen `dd` before!

the only discrepancy between your post and my experience was that the partition command did not print "Could not mount disk2s2 after erase" the way you show.

Re: Technical Notes on O3D

elenzil — Tue, 28 Apr 2009 11:54:26 -0000

it seems like O3D + google native would be an awesome combo.
the computation you can do on the GPU is pretty impressive these days (eg calculating julia sets, simple waves etc), but for really crunching data like in say a large gravity or fluid simulation i think you need a general-purpose CPU and i'm not sure that V8 or tamarin will really satisfy.

on another topic, what's the coolest O3D demo peeps have seen so far ?
has anyone used render targets + environment mapping do do dynamic reflections yet ? all the pieces are sorta just sitting there.

Re: Technical Notes on O3D

elenzil — Thu, 23 Apr 2009 14:43:22 -0000

thanks for taking the time to look at that .as code, zwetan.
i tried cacheAsBitmap as you suggested, but not much change (presuming i used it correctly - just shape.cacheAsBitmap = true ?)

i guess my fundamental take here is that rasterizing 400 rectangles should not be anywhere close to a bottleneck. i've got way more interesting things to do with my programming time than fight that.

compare, for example, to this demo which renders 1000 rotating bump-and-environment-mapped utah teapots (3783 triangles each) at 30 to 40+ FPS on the same exact machine, and barely bumps the CPU at all. and it uses javascript instead of actionscript, and there's no compilation step.

Re: Technical Notes on O3D

elenzil — Thu, 23 Apr 2009 00:41:08 -0000

vista

Re: Technical Notes on O3D

elenzil — Wed, 22 Apr 2009 18:32:57 -0000

huh. many thanks for looking at the demo. other folks have mentioned it gives errors. where to these errors show up ? do i need a debugger installed ? but in any event i doubt it's the errors which are giving it trouble; at small window sizes it uses just a tiny portion of the CPU.

Re: Technical Notes on O3D

elenzil — Wed, 22 Apr 2009 18:30:31 -0000

well it doesn't behave incorrectly, but it chews up nearly all the CPU of my pretty zippy machine at say 1000 x 1000 pixels.
it's clearly the rasterization which is the issue. http://elenzil.com/flash/fl...

Re: Technical Notes on O3D

elenzil — Wed, 22 Apr 2009 18:19:53 -0000

now *this* feels like the web-based graphics environment i've been looking for !
i'll try to port my "400 rotating squares" demo, which imo exposes Flash10 as a dog, to it tonight.

Re: PushButton Labs at Flash Gaming Summit and GDC09

elenzil — Mon, 30 Mar 2009 20:31:17 -0000

gotcha. that jives with my impression of the industry. :(

Re: PushButton Labs at Flash Gaming Summit and GDC09

elenzil — Mon, 30 Mar 2009 14:40:21 -0000

hey ben, could you elaborate on "seeing the job market totally packed" ?
do you mean that unemployment in the games industry is low ?

Re: Tip: Setting Up Flex Builder The Sane Way

elenzil — Thu, 22 Jan 2009 20:41:24 -0000

for those who may come across this post on their search to learning how to set up a command-line-only Flex environment, and who also know previously zilch about Flex/AS/Flash, i sketch the steps very roughly here: http://elenzil.com/flash/fl...

Re: Tip: Setting Up Flex Builder The Sane Way

elenzil — Mon, 05 Jan 2009 17:06:54 -0000

heh. interesting; i look forward to the post !

thanks for this Flex tip, btw.
since my comment above i started looking for a framework in which to write some simple 3D apps in a portable, easy-to-consume way and have decided to try out Flash 10. i'm hoping the command-line-only approach will work out, but i'll probably give the IDE a look as well.

Re: Tip: Setting Up Flex Builder The Sane Way

elenzil — Sat, 13 Dec 2008 23:28:09 -0000

hey ben, it's orion elenzil.
any thoughts on the new google native x86 stuff vs the recent work in the various javascript cores ?