Windows version is half the speed then Mac version in terms of collision for me

Sorry to be back so soon, I actually wanted to drop this since I have a working game on windows, but people want a full speed windows version, this issue was somewhat addressed in the thread below, but believe it needs it’s own thread to focus on.

So as the title says my collisions are cutting my game’s speed in half when on windows, regardless if I am running the exe or sdk, it is the same mac machine just the platform is different (bootcamp enables me to run windows 10), and windows version runs at 14fps while mac runs at 30fps (my cap).

I manage to record the pstats in a image on the windows version (it’s below, I would get them for the mac, but I cannot get pstats working, though it should not matter much because mac is running at the full capped 30fps)
So in the previous thread, me and Thaumaturge concluded that the slow down in windows was the collisions (as you can see above) which would be fine, I mean I could try octree, or combining the collision nodes into less nodes or the like for speed ups.

But there would always be that problem that the mac version is faster and I can do more on it, which wouldn’t be problem if I developed on windows, but I develop on mac, having to check on the windows version often would be difficult for me (especially since I don’t have a windows machine in my possession, I had to barrow the macbook with bootcamp)

I am so thankful for you guys help, and I am sorry for bugging you so soon, and thank you to those willing to help.

Let’s first establish whether we are comparing apples to apples. Are you using the 64-bit version on Windows? Are you getting this performance in both cases in the build produced by build_apps, or with the development version of Panda? The build produced by build_apps is significantly more optimized than the “normal” installation of Panda.

You should optimize your collisions one way or the other, though; it is usually possible to get good performance benefits by octreefying or even just using something like world.subdivideCollisions(4).

yes, it is the same machine, I always use 64bit in my bootcamps, I don’t see any benefits to using x86 unless the machine requires so, and yes tested both bdist and sdk, the difference between the two is model loading is faster on the bdist, but the collision remains the same, even with other users complaining the same thing.

Thanks for the optimization tip, I will use if I see slowdown when I am developing.

Edit: I am going to try your subdivdeCollsion method on the windows version, give me a minute.
EDIT2: so I tried and kept getting “NameError: name ‘CollisionNode’ is not defined”, I am now going to attempt octreefy tomorrow with some code found on the forums.

I couldn’t get the octreefy code to work, though subdivdeCollision I decided to look into more, I went to py file responsible and added the collisionNode import to finally get it to work, but it turned out, it ended up breaking my game, I assume that it must have changed the collision nodes names and I cannot have it do that.

If octreefy does the same and touches the names, then it is also not the answer for me, I am appreciative for the tips though, thank you rbd.

EDIT: my brother toke back his pc, so I cannot test this for the time being, my apologies.