Hi, I get very poor performance with [multimodel] Models are loading fine (with few warnings message about 'material not found') but if I want to change the model number on the right inlet of [multimodel] cpu use increase to 100% and I have frames drops on the gemwin
Any ideas about what it could be ? Do I need to fill a bug report ?
with : pd vanilla compiled from svn on ubuntu 10.10 64bits, gem compiled from svn too
ps : I have many gem patches, with models, shaders, particules, repeated gemlist, etc on a brand new laptop (with nividia 480) and all my patches are working great (i mean a loooot of fps) except this one with multimodel.
pierre
Le 05/04/11 16:27, Pierre a écrit :
Hi, I get very poor performance with [multimodel] Models are loading fine (with few warnings message about 'material not found') but if I want to change the model number on the right inlet of [multimodel] cpu use increase to 100% and I have frames drops on the gemwin
Any ideas about what it could be ? Do I need to fill a bug report ?
with : pd vanilla compiled from svn on ubuntu 10.10 64bits, gem compiled from svn too
ps : I have many gem patches, with models, shaders, particules, repeated gemlist, etc on a brand new laptop (with nividia 480) and all my patches are working great (i mean a loooot of fps) except this one with multimodel.
pierre
Ok, I've just compiled the Gem stable release 0.92.3 (Gem compiled as before against pdvanilla svn 0.43 latest sources), and all the bottlenecks seams to be gone, I have a nice frame rate even with [multimodel]. So it seams that the problem with [multimodel] come from the lastest gem sources
p.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-04-06 16:32, Pierre wrote:
Ok, I've just compiled the Gem stable release 0.92.3 (Gem compiled as before against pdvanilla svn 0.43 latest sources), and all the bottlenecks seams to be gone, I have a nice frame rate even with [multimodel]. So it seams that the problem with [multimodel] come from the lastest gem sources
interesting. thanks for testing. please file a bug-report at the gem bug-tracker.
fgamsdr IOhannes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-04-06 17:58, IOhannes m zmoelnig wrote:
interesting. thanks for testing. please file a bug-report at the gem bug-tracker.
and while doing so, it would be great if you could also provide a simple test patch that triggers the unwanted behaviour. i happen to have only a limited number models lying on my harddisk.
fgamsdr IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
IOhannes m zmoelnig -
Pierre