Edit: Thanks Conitec for your great support by moving this topic to a forum of no interest.
------------------------------------------------------------

Dear Conitec Team,
Dear JCL,

As a longstanding user of Gamestudio and Intense Illusions` Pathfinding solution I`m very sad to mention that IntenseX and Intense Pathfinding will most likely being discontinued because of a "memory bug" that is caused by the Gamestudio Engine.

Just if you missed it: Intense X is a big, if not the biggest advancement for GameStudio within the last years and allows both newbies and advanced users like me to realize their game design ideas without investing hundrets of hours just to get a working prototype of own software solutions. It brings the idea behind GameStudio to a conclusion and has real potential to encourage potentially new customers to purchase your game development kit altogether with IntenseX.

We, the still increasing community of Intense X and Intense Pathfinding are waiting for new versions and updates of this great software solution and are more than afraid that you guys of Conitec don`t even mention that everything is dependant on you and your support team. Please reconsider your work in view of GameStudios future that is more and more pending on solutions like IntenseX.

Best regards

I agree with Rondidon!

Agreed !!

Because intenseX takes the most of the work for a fps. it takes the code for moving shooting weapon inventory and so on... i really think you should support the guy, because if it will stay like this and nothing changes, then maybe i will give up 3DGS. IX is sooo important!
you really should think about it.

just my 2 cents.

Agreed!

Lets put it this way:
if there is a Memory Bug, it should be adressed anyhow.
Or a workaround should be given.
Its a core part of the engine to run stable.
(Where I have to say that gamestudio is a very stable
product compared to other engines)

Agree with u guys

agreed.

Agreed. Dont let IntenseX die!

intensex should not die. ever.

If there really is a memory bug then I'd like to see it fixed - independently from IntenseX as it may be a problem for other programs as well.

SED still has this annoying memory leak btw.