Unreal Map Editor (2k3)

[Colorblind]

Although I'm sure it's really powerful, it crashes more then morrowind and for some reason just stopped working. Anyone else have lots of problems with this editor?

[RAY16]

I tried mapping a few times, but i got frustrated and gave up. While i was using it, i got a decent amount of crashes. But it never just stoped working, just annoying crashes. You could re-install the latest patch (I think every patch has UED in it, but i'm not sure), or re-install the game.

[Hobbes874]

yeah mapping it's tough and fustrating :(

[Colorblind]

I just don't want to map if I have to deal with saving every time I make a friggen change. That's just stupid. I miss genedit - nice editor, but wasn't very buggy and was pretty easy to use.

[Rhenna]

Been mapping with UnrealED for years. The "old" editor was written in Visual BASIC and was *NOT* very stable. The new editors, including 2K3 are in C++ and while not crashproof, are far more reliable.

Do you have the "autosave" option on? Go to View > Advanced Options > Advanced > AutoSave > True. Your map progress will be saved as Auto1, Auto2, etc. every 5 minutes. If it crashes, just find the latest backup. (It loops back after Auto9.)

Mostly an UnrealED 2.0 person; only have a few dozen hours on the UT2K3 editor. The new editor wants 32-bit color, so check that. And, the V1.0 and V2.0 editors are picky with regard to video cards and drivers. I'm not happy with the Nvidia 43.45 drivers within UnrealED 2.0, for example. Stable, but things look weird. I've tried video cards that were all but unusable with the earlier editors. What card are you using?

I'll try and help you if I possibly can.

*update* OK, I saw your G4 Ti4600 on another post. You shouldn't have a stability or crashing issue with that, just possibly a rendering issue under certain circumstances.

[Colorblind]

Hmm... well, I'm running the 43.45 drivers, so that might be an issue. But it isn't stable for me and for some reason the editor will load but all four viewpoints don't show up.

I'll mess with drivers and see what happens, but I'm not going to make this a big bug hunt. I'm trying to stay away from computer repair so I can get my life back *Yeah right*

*sigh* i just hate computers..

[Rhenna]

I really wouldn't mess with your drivers; they shouldn't be the cause of the editor crashing, just some visual anomalies that wouldn't affect stability. I don't want you to wind up with a bunch of mixed driver files or other problems.

Can I ask if you have previous UnrealED experience? I do so only because there are, apparantly, some additional pitfalls in the UT2K3 editor that can cause it to crash out to the desktop, where those same actions were OK in the earlier editors.

[Colorblind]

I've played with the org. editor, but nothing fancy. I have not even gotten through the intro tutorials on this version of the editor before this happened..

[Colorblind]

Alright, sorry for the double post, here is what the problem looks like:

[Rhenna]

I spent some time installing the editor (Version 3) on a 2nd PC, and lo and behold, I had no viewports on startup.

Things were going nowhere until I chose CLOSEALL under VIEW > VIEWPORTS, and then NEW VIEWPORT. (Even though the viewport was already closed.) (?) Prior to selecting CLOSEALL, the NEW VIEWPORT command did nothing.

From then on, everything was OK. I hope it's as easy as that. Oh, and the next thing that usually frustrates people is trying to work with anti-aliasing on. Don't do this; you'll be pounding your head into the keyboard after a few minutes.

Sorry for the delay. Hope the links helped.

[Colorblind]

Well, I tried that and nothing happened... *sniffle*

I tried restarting the program after doing that with no change..

One other thing it does: the screen gets lighter (I think that's just from changing the brightness in Unreal ...

[Rhenna]

I was running a Radeon 8500 on the PC I was using to work with the V3.0 editor. Everything was OK, but when I later installed a different 8500, (faster clock, 128Mb RAM), and got lazy about uninstalling/reinstalling the video driver, the only app that behaved strangely was the editor. On startup, the "splash" screen would get bright after a few seconds, and within the editor, everything would get a washed-out look, like the gamma setting had gone nuts. Doing the "right thing", driver-wise, cleared up the problem. (OK, like I said, I got lazy...)

This was the issue I mentioned in my PM. Please don't mess with your drivers if you know they're OK; just be sure your D3D settings are as 'plain jane' as they can be, aside from 32-bit color. I'll submit the viewport issue to the UT gods and see what happens.

***update***

1.) Check out this link for more on the viewport problem.
http://www.master-builder.org.uk/the_GoaT/misc_faq_ued3.htm

2.) If THAT doesn't work, try renaming your original unrealed.ini to unrealed.xyz, for example. The editor should build a new one on startup.
"defunrealed.ini" is a default .ini, if needed.

3.) Seems the "gamma" issue is DirectX9-related. Brightness in the editor is SUPPOSED to be linked to the game settings. This was how the editor was when it shipped. DX9 clobbered it, and the later patches fixed it again.

[Colorblind]

HAHAH! FIXED IT!

Just had to configure the viewports like that FAQ said, thanks!

[Rhenna]

Great! Maybe I'll be more help, next time. (Then again, maybe not...)

Perhaps you can let me check out your 1st map when it's finished?

[Colorblind]

Sure, its a nice cube :P

If I can figure out the editor I'll let you take a look at my maps ;)

[RADiator]

Originally posted by Colorblind
Sure, its a nice cube :P

If I can figure out the editor I'll let you take a look at my maps ;) LET ME LET ME!! I LIKE NEW UT2K3 MAPS!