As I'm doing some non-trivial API changes in the Castle Game Engine 6.3 (to be released as 6.4), I test the engine on various real-life code using the Castle Game (like your games), to judge how much compatibility did I break :)
I want to minimize the compatibility break as much as possible, and only mark stuff as "deprecated", but it's not (easily) possible for some of the latest changes, so unfortunately some changes in user (game) code will be necessary.
In this case, some unit renames in CGE 6.3 are affecting your code. The affected units can be just removed.
Also, Window.DoRender is not available, since at least CGE 6.2. We could provide a compatibility "patch" in the engine for it (keep it defined but deprecated), but it was only public for a short time, and it's really a bit dirty -- so I would prefer to just keep it private :) More comments in the commits.
As I'm doing some non-trivial API changes in the Castle Game Engine 6.3 (to be released as 6.4), I test the engine on various real-life code using the Castle Game (like your games), to judge how much compatibility did I break :)
I want to minimize the compatibility break as much as possible, and only mark stuff as "deprecated", but it's not (easily) possible for some of the latest changes, so unfortunately some changes in user (game) code will be necessary.
In this case, some unit renames in CGE 6.3 are affecting your code. The affected units can be just removed.
Also, Window.DoRender is not available, since at least CGE 6.2. We could provide a compatibility "patch" in the engine for it (keep it defined but deprecated), but it was only public for a short time, and it's really a bit dirty -- so I would prefer to just keep it private :) More comments in the commits.
Regards!