<SHC> I really like the idea about porting bullet 3
<SHC> right now, I have no experience with it (not porting but using it) so I'm now setting up a test workspace in VS2015
<SHC> Yeah, I would also like to integrate bullet into my engine, so that would be pretty good to have.
<elect> I took a look to their repo
<elect> it seems they are still in the phase of transporting bullet2 to 3
<elect> Im writing down the validation right now
<elect> I need the stl
<SHC> Standard Template Library?
<elect> I think so
<elect> We are gonna need some collision detection in the future for our engine and therefore I was looking at jbullet
<SHC> How are you planning to port it? You write JNI code? or port it to java manually by hand?
<elect> I dont want any binding
<elect> I want pure java code
<elect> so that we can tune everything
<SHC> So porting by hand? That's a lot of code there..
<elect> I need hardbody collision for the moment
<SHC> So we chose the hard path of thorns,.. so shall we spend some days getting used to bullet 3 in C++ first?
<elect> I was also thinking if launching a kickstarter could make any sense
<SHC> Aren't you making it opensource? I mean, working it on free time?
<elect> opensource for sure
<elect> I will work on it during some part of my work and in my free time
<elect> if we go for the port
<elect> I'd like 100% java so that we can also choose to avoid some class instances for performance and memory footprint
<SHC> My idea is a bit different, we can avoid the vector classes, like btVec etc., and instead construct the structs in JNI code?
<elect> we shall discuss the pro and vs
<elect> actually I was thinking to rely on JOML
<elect> from kaihh
<elect> it looks very good for performances
<SHC> That's a good idea too, I thought so since constructing objects is very expencive but struct instances is not..
<elect> so at least the math part is "already done"
<SHC> haha yeah, agreed, we shall be using JOML. And the bindings? I have to see an overview of bullet and read some demos.
<elect> what is your dev os & machine, SHC?
<elect> Im using an i5 & 770 on 15.04 x64
<SHC> Windows 10, i7 4790k, NVIDIA GTX 750 Ti and 16 GB RAM.
<elect> or i5 & 680
<elect> modern enough
<elect> (for opencl support)
<SHC> Yeah, I think OpenCL is supported even on GTX 210
<elect> yeah, but it is not mature
<SHC> That's the minimum I heard
<elect> I read the guide, they say cl kernels are very likely to crash for a large number of reasons
<elect> moreover they cannot use cpu as opencl devices, dont know why
<elect> does lwjgl has a opencl binding?
<elect> I guess so
<SHC> Yes, LWJGL had OpenCL bindings
<elect> nice, we can do then something generic and everyone will choose what he likes most
<elect> like joml
<elect> I already cloned and built it
<elect> most of examples run
<elect> just a couple crashes
<SHC> Oh I'm now reading the manual.
<elect> the problem is that they made a browser windows example and when you open it selects automatically the last example you run.
This means once it crashes I have to clean and clone again, since everytime I open from that moment going on it keep crashing
(coz it tries to open the same example)
<elect> anyway the opencl support is experimental
<SHC> Did you create a repo?
<elect> not yet
<elect> I am still in the decision phase
<SHC> oh kk
<elect> the thing is that it relies of course also on acceleration structures
<elect> I am just starting with that too
Just posting it here in case anyone would like to know what happened behind the scenes in the IRC.