an even quicker fix would be to just switch to GST Builder. After i noticed the same problem I tried it out with GST, the third party compiler, and im pretty sure id does not eat ur resources the same way as SED does.

I have this exact same problem.
Over time it also gets worse...

After some time SED will stop opening on my computer.
It's process only shows up in the list of running processes.
The only way to get SED to open for me after this period of time is to reformat and install gamestudio.

So when this happens I usually switch to MSVC++ or GSTBuilder.
Although GSTBuilder erases your code if you open a file but don't make changes to it or save it then close it.

Use Notepad or Wordpad instead. If only Conitec would ever release the update (even as a public beta), users could get the fixed and updated version of SED. 10 months is rediculous . I've almost quite literally stopped working on my 3D game because I need the external textures feature more than anything. There's hardly any changes going on in the base beta version as well - two or three things per month. If they'd release a public beta, they can get more fixed than that in the same time period. So many users are getting impatient with the release of the update....

the update will be released very soon... I would say ~2-4 weeks maxiumum..

But I would also prefer public betas (although i am a beta tester)

Yes, I agree with you, but the new beta SED still have some problems. For example, in my computer SED(beta) crashs when I try to open a wdl file. So, I can not use. Imagine if that happens for you also.

Quote:

---

this was a real old bug (fixed in 2001 I think), that shouldn't be in the actual release.
Can you post some more info about that?

---

Sorry, it turns out that I've been using an outdated version of GST-Builder.
It doesn't do that anymore with the update.

Same thing as by me.

Best regards
XeXeS

I'm also having this problem.. After around 2 hours of programming, switching between programs gets problematic, and some buttons apear white. Restarting SED fixes it, but it's still quite annoying.

I've not experieced the "major" problems others attest to, but I can say that the SED memory management is, to put it mildly, "weird"...

I open up SED 1.2.8, and it has a un-stable footprint of 13 meg. Left alone, this footprint slowly rises. IT shouldn't.

But here is the weird part. I left SED open last night for about 12 hours and the footprint this morning registers at 1.3 megs...ten times less!!!

And of course, the "fast type" issue is still there. If you type normally, you'll get about 8 to 10 percent CPU usage on SED...by comparason, notepad and word only use less than 4% under the same circumstance. If you type fast, SED jumps up to 50 or 60% CPU usage...notepad and word barely make it to 10%.

I've tried this same thing on the beta 1.3.0f and the same behaiviour is there, including a 15 Meg footprint upon opening which also slowly rises.

I've not experienced major problems, but there is definitely a bug(s) in there somewhere...