A contribution outside my domain of e :
In Unity 5.0, the SDK generates all the data required to handle fast movement. You just enable continuous collision detection and it works. PhysX3 features an algorithm used to detect whether the expensive CCD simulation is actually needed given the current body velocity or a default discreet would do just fine. It’s activated once you enable the CCD.
Should be "discrete", not "discreet" :) Ha ha!
http://blogs.unity3d.com/2014/07/08/high-performance-physics-in-unity-5/
Shame on your Angel Garcia :) Just kidding... but, shame on India as usual - no representation at all :(
Friday, October 16, 2015
Saturday, February 14, 2015
Perl Debugger Broken?
DB<38> b 102 ($mod eq 'modn')
DB<39> c
main::parametrize(./kitmaker.pl:204):
204: @compare_params = ($ref_line =~ /(?<!\w)((?:[0-9.]{2,}|[0-9]+)(?:e[+-]?\d+)?)/g );
DB<39> p $mod
dn
See? Instead of stopping at 102, it stopped at 204. Wha??
Off topic, a gem from Marty O'Brien, die Meister :
If you've done a serious script and thumped your head trying to figure out what's going on, you know valuable it is to be able to stop-when-error-encountered - instead of using stupid things like b and c..
DB<39> c
main::parametrize(./kitmaker.pl:204):
204: @compare_params = ($ref_line =~ /(?<!\w)((?:[0-9.]{2,}|[0-9]+)(?:e[+-]?\d+)?)/g );
DB<39> p $mod
dn
See? Instead of stopping at 102, it stopped at 204. Wha??
Off topic, a gem from Marty O'Brien, die Meister :
If you've done a serious script and thumped your head trying to figure out what's going on, you know valuable it is to be able to stop-when-error-encountered - instead of using stupid things like b and c..
our $warn_flag = 0;
$SIG{__WARN__} = sub { $warn_flag = 1; CORE::warn(@_) };
...
for $i (1 .. 1_000_000_000) {
do_something_that_might_warn();
$DB::single ||= $warn_flag;
$warn_flag = 0;
}
Monday, February 2, 2015
Google, Listening? Should be An Easy One
Google spreadsheets : You use the Text Font dropdown to pick a colour for the text in a cell or row, now, please retain that colour selection for the dropdown so that the user can then apply that same colour to a new selection by just clicking on the dropdown and not having "select" again!
Get it? Even M$ has this right. Shame on ye.
Get it? Even M$ has this right. Shame on ye.
Thursday, January 8, 2015
I Need a Hero (gEDA Schematic Capture)
First, praise :
Good, they have the ability to click on a component to select - LTspice doesn't.
You can click and drag to move a component. Good. You don't have to "launch the move command" to then select a component to move.
But, it's still a ridiculously crappy platform. Who made this? Is it people who were pissed off at ExpressPCB.com? Obviously these folks have never seen the Cadence model.
You NEED a command interpreter window. Hell! I had one in the emulator I built to talk to my chip - and making macros was a breeze and all I know is the spelling of object oriented programming. I just did it because it was a good thing to do. You need to have a log! You need window numbers. That's just the right way to do things.
You need extendability and customizability! You need to be able to add menus to do your own things!
Why didn't they think about providing ways to go from the design to the other tools in the chain - netlisting/simulating/waveform-viewing/layout. Crap!
Then, some obvious missing features and bugs :
What else do we need? We need a hero at a university to provide the entire MOSIS PDK in gEDA for the little fellow to use :) So, generate libraries for each TSMC process that MOSIS has models for - then the little man can keep practising IC design at home - keep his skills sharp.
Good, they have the ability to click on a component to select - LTspice doesn't.
You can click and drag to move a component. Good. You don't have to "launch the move command" to then select a component to move.
But, it's still a ridiculously crappy platform. Who made this? Is it people who were pissed off at ExpressPCB.com? Obviously these folks have never seen the Cadence model.
You NEED a command interpreter window. Hell! I had one in the emulator I built to talk to my chip - and making macros was a breeze and all I know is the spelling of object oriented programming. I just did it because it was a good thing to do. You need to have a log! You need window numbers. That's just the right way to do things.
You need extendability and customizability! You need to be able to add menus to do your own things!
Why didn't they think about providing ways to go from the design to the other tools in the chain - netlisting/simulating/waveform-viewing/layout. Crap!
Then, some obvious missing features and bugs :
- No way to flip a component sideways. Whoever thought about doing a differential pair in a PCB. Idiots!
- You've a bunch of wires - and it does solder joints automatically. Great. Now, click and drag on one of them, and it just completely disconnects. WT*!!? Come on guys!
- Fit the schematic with the 'f' key. Please :)
What else do we need? We need a hero at a university to provide the entire MOSIS PDK in gEDA for the little fellow to use :) So, generate libraries for each TSMC process that MOSIS has models for - then the little man can keep practising IC design at home - keep his skills sharp.
Subscribe to:
Comments (Atom)