it seems that it has something to do with text3dfirst the text was
written directly into the box.i changed that to message symbol
text.did not change the crash
Zitat von IOhannes m zmoelnig zmoel...@iem.at:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-08-31
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-08-31 13:15, bra...@subnet.at wrote:
maybe an idea where to start?
well, start form your patch and remove everything that is not Gem.
then copy everything left into a flat patch.
then remove entire gemchains until only the one that causes
oohothis may take some time i fear
Zitat von IOhannes m zmoelnig zmoel...@iem.at:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-08-31 13:15, bra...@subnet.at wrote:
maybe an idea where to start?
well, start form your patch and remove everything that is not Gem.
then copy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-08-29 18:46, bra...@subnet.at wrote:
- what get's printed to the pd-console before the crash? what get's
printed to the console?
nothingpd just disapear
never!
i think this has been mentioned on this list a couple of times, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-08-30 11:51, bra...@subnet.at wrote:
hmmmthank you
attached the pd.log file and the file pdVV.txt -verbose -verbose prints...
thanks.
the pd.log doesn't do much, but pdVV.txt shows a bit.
#1 are you sure that this is Gem-0.93.1,
On Tue, 30 Aug 2011, IOhannes m zmoelnig wrote:
$ C:\Programme\pd\bin\pd.com -stderr -open patch.pd 2 pd.log
does 2 exist in that shell ?
my memory is that I learned 2 in 1997 as part of bash, just like 666
other features that weren't in COMMAND.COM.
Was that added in Windows 4.0, or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-08-30 18:56, bra...@subnet.at wrote:
sorry first...i was out of office...lets start
np.
at least we now know that it is not the plugins that are problematic.
i fear that you really have to trim down the patch to a minimal set of
objects
