Can we see some specs Speed, OS, Graphics Card, from this target machine? Maybe we are looking at the problem from wrong perspective.
The thing is you say Blitz3d apps are fine, but not BMAX.
I think you need to create the smallest program that demonstrates the problem. Something without your framework involved.
If its simple enough we can then create same program in Blitz2d or Blitz3d and see if problem persists. If it does its the machine. And from there you just tell people to disable 3rd party widgets.
If not it should be simple to figure what is different. There really isnt much to BMAX windows processing vs. Blitz except for sound subsystem and automatic Garbage collection.
Your event based input solution is still a much better solution so dont worry about the work you did being wasted.
Another thing to consider. Does your test App use the Framework command to remove BMAX subsystems that are not currently in use? Maybe your picking up something else during compile time thats interfering.
Doug Stastny
The thing is you say Blitz3d apps are fine, but not BMAX.
I think you need to create the smallest program that demonstrates the problem. Something without your framework involved.
If its simple enough we can then create same program in Blitz2d or Blitz3d and see if problem persists. If it does its the machine. And from there you just tell people to disable 3rd party widgets.
If not it should be simple to figure what is different. There really isnt much to BMAX windows processing vs. Blitz except for sound subsystem and automatic Garbage collection.
Your event based input solution is still a much better solution so dont worry about the work you did being wasted.
Another thing to consider. Does your test App use the Framework command to remove BMAX subsystems that are not currently in use? Maybe your picking up something else during compile time thats interfering.
Doug Stastny