I was going through the tutorial which also requires pinball movement and after adding the 'milk blocks' then they were the only thing visible.
Closing and reopening fixed it. have yet to go through the tutorial again to see if I can isolate when the disappearing occurs.
Edit: It was actually a bouncing ball movement I used. And I went through tutorial again and it didnt happen.
I was going through the tutorial which also requires pinball movement and after adding the 'milk blocks' then they were the only thing visible.
Closing and reopening fixed it. have yet to go through the tutorial again to see if I can isolate when the disappearing occurs.
Edit: It was actually a bouncing ball movement I used. And I went through tutorial again and it didnt happen.
Close/Reopen fixes...
I don't feel like having to keep closing and reopening the program everytime this happens. I feel that if I'm working on a game, I should be able to get what I need done in one sitting, I shouldn't need to keep restarting MMF2. It's a sign of a relitively unstable program.
Close/Reopen fixes...
I don't feel like having to keep closing and reopening the program everytime this happens. I feel that if I'm working on a game, I should be able to get what I need done in one sitting, I shouldn't need to keep restarting MMF2. It's a sign of a relitively unstable program.
We already had this problem during the beta tests and I thought it was fixed, but it seems everything was not fixed. I'll try to reproduce it on my side, but if someone could find a way to reproduce it, that would be great.Thanks!
(ps: I think it's only a simple object order problem, not a big issue - but hard to locate)
Yves.
PPS: JL32BIT, MMF2 is NOT a completely new engine, some parts are new or have been completely redone, that true, but a part is still the same as in MMF 1.5.
We already had this problem during the beta tests and I thought it was fixed, but it seems everything was not fixed. I'll try to reproduce it on my side, but if someone could find a way to reproduce it, that would be great.
(ps: I think it's only a simple object order problem, not a big issue - but hard to locate)
Yves.
PPS: JL32BIT, MMF2 is NOT a completely new engine, some parts are new or have been completely redone, that true, but a part is still the same as in MMF 1.5.
[]PPS: JL32BIT, MMF2 is NOT a completely new engine, some parts are new or have been completely redone, that true, but a part is still the same as in MMF 1.5. [/]
Ah sorry, my mistake. <img src="/center/images/graemlins/laugh.gif" alt="" /> Wasn't it said that MMF2 was rewritten in C rather than assembly? I thought that that alone would isolate bugs that moved from 1.5 to 2.
[]PPS: JL32BIT, MMF2 is NOT a completely new engine, some parts are new or have been completely redone, that true, but a part is still the same as in MMF 1.5. [/]
Ah sorry, my mistake. <img src="/center/images/graemlins/laugh.gif" alt="" /> Wasn't it said that MMF2 was rewritten in C rather than assembly? I thought that that alone would isolate bugs that moved from 1.5 to 2.
>> Wasn't it said that MMF2 was rewritten in C rather than assembly?
The event engine was rewritten in C, but it's only a part of MMF2 and even if it was rewritten in C, lots of functions work the same, some 1.5 bugs are still present in 2.0.
Yves.
>> Wasn't it said that MMF2 was rewritten in C rather than assembly?
The event engine was rewritten in C, but it's only a part of MMF2 and even if it was rewritten in C, lots of functions work the same, some 1.5 bugs are still present in 2.0.
Yves.
Posting Permissions
Reply With Quote