Announcement

Collapse
No announcement yet.

Several MAJOR concerns with UT3ED.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Several MAJOR concerns with UT3ED.

    Ok, as of lately I have been having alot of SERIOUS problems with UnrealED. First of all over the last week I have been Working on an outdoor map, my first to be exact, and I can never build it.

    Here are my problems:

    1: Material Editor will not take textures from generic browser.
    2: Extremely long build times 40+ minutes.
    3: MAP will NOT finish building, at about 45 mins editor crashes and "UT3.exe has stopped working"


    I don't know if this will help anyone, but I'm running a Windows Vista Home Premium system with 2.5GB of RAM, a nVidia AVGA e-Geoforce 9600 GT, and a 2GHZ Intel Dual Core Processor (E4400).

    I hope someone can help me.

    #2
    Go to the Tools Tab and "check map for errors" try using it and see what kind of errors your map has, it could have something thats not working or have conflicting assets that might be causing the crashes.

    Comment


      #3
      1.
      I need more information to help you with this one. By textures do you mean already cooked textures you are trying to make a new material instance from? or do you mean something you have imported and is not taking to your material? or do you mean you are assigning materials to things in your level that are not appearing in game leaving you with a checker board (default) material?

      2&3.
      it is a good idea to have your log open just prior to hitting the build button.
      The log is part of the generic browser now and is just a tab. click the tab and then hit build and you will get to see what the editor is doing and where it is taking longer to calculate etc.

      You can also view the log after the fact by going here:

      \My Documents\My Games\Unreal Tournament 3\UTGame\Logs

      I am pretty sure it will be LaunchLog, though there are only three possibilities. Launch.log, Launch_2.log or dedicated server.log(dedicated server.log will only exist if you have ever run a server from your box).

      dave

      Comment

      Working...
      X