finally i found it :) in the init function i used SetFloat... and that caused the problem when trying GetVector
this part is solved, thanks for pointing me towards the right direction
thank you both for getting back. i'll double check again if the ID has been used before. however i am totally lost with this upgrading. since the plugin worked flawless in previous versions and after getting it to compile with r20 it crashes so often.
what does it mean when the debugger holds at a line like that,
Vector rndoffset = bc->GetVector(RNDOFFSET);
with a message "CINEMA 4D.exe hat einen Haltepunkt ausgelöst."
it simply means that the bc pointer is likely to be invalid.
according to this problem, the pointer must be valid, i am checking it like
if (!bc) return nullptr;
and if i run the plugin without debugging that one works. additional information, the line before that one throwing the exeption is:
Float lightSpeedFactor = bc->GetFloat(LIGHTSPEEDFACTOR);
so, if bc wasn't valid, that one should give the same exception, right?
so far, i replaced it by
Vector rndoffset = Vector(0);// bc->GetVector(RNDOFFSET);
and the whole plugin works. this is really strange
thank you Riccardo, i must admit that i just followed the adjustments needed to make it compile under r20. the code worked like that in previous versions and the plugin itself is quite old so i didn't question the code itself.
maybe it is time to do so and walk thru every line
as i am currently walking thru the millions of warnings i get, what shall i think of such a warning?
The function GetDDescription has 803 lines, this exceeds the limit of 500 lines.
edit: this now appears for a bunch of functions i use in the plugin. does it mean the compiler isn't checking the rest of the lines? isn't it set a bit to low?