For direct access use https://forums.oldunreal.com
It's been quite a while since oldunreal had an overhaul, but we are moving to another server which require some updates and changes. The biggest change is the migration of our old reliable YaBB forum to phpBB. This system expects you to login with your username and old password known from YaBB.
If you experience any problems there is also the usual "password forgotten" function. Don't forget to clear your browser cache!
If you have any further concerns feel free to contact me: Smirftsch@oldunreal.com
It's been quite a while since oldunreal had an overhaul, but we are moving to another server which require some updates and changes. The biggest change is the migration of our old reliable YaBB forum to phpBB. This system expects you to login with your username and old password known from YaBB.
If you experience any problems there is also the usual "password forgotten" function. Don't forget to clear your browser cache!
If you have any further concerns feel free to contact me: Smirftsch@oldunreal.com
Unreal Tournament Editor problem
Moderator: Buggie
-
Leviro
- OldUnreal Member
- Posts: 5
- Joined: Sat Mar 13, 2010 9:49 am
Unreal Tournament Editor problem
I have recently got Unreal Tournament off a friend. It came with Unreal Editor 2.0 wich on my friends pc works fine, but on mine, every time I try to move the camera it just goes crazy and moves all over the place. This is very annoying as it prevents me from using the editor at all. Neither me nor my friend have any idea as to whats happaning, so any help would be appreciated.
-
GreatEmerald
- OldUnreal Member
- Posts: 5347
- Joined: Mon May 21, 2007 2:30 pm
Re: Unreal Tournament Editor problem
Open UnrealEd 2.0 and look at the lower left corner. You should see three lines, press them and see if that changes anything, if not, press them again and repeat. You could also try right-clicking on your 3D viewport and selecting another renderer from the list (Direct3D or Software).
-
Leviro
- OldUnreal Member
- Posts: 5
- Joined: Sat Mar 13, 2010 9:49 am
Re: Unreal Tournament Editor problem
Thanks for the reply, it didnt work though. Ill try to explain the problem better:
I open up the editor, pick the view I want, click on the view to move around (left or right click), and the without moving the mouse, the whole map spins if its in a 3D mode, or it just moves up to one corner if its in a 2D mode.
I open up the editor, pick the view I want, click on the view to move around (left or right click), and the without moving the mouse, the whole map spins if its in a 3D mode, or it just moves up to one corner if its in a 2D mode.
-
GreatEmerald
- OldUnreal Member
- Posts: 5347
- Joined: Mon May 21, 2007 2:30 pm
Re: Unreal Tournament Editor problem
That's really strange... Does it say anything interesting in your Editor.log?
-
Leviro
- OldUnreal Member
- Posts: 5
- Joined: Sat Mar 13, 2010 9:49 am
Re: Unreal Tournament Editor problem
Nope theres nothing there at all, just a blank document. I have a feeling its my computer and just in case Im going to try the editor on a laptop.
-
GreatEmerald
- OldUnreal Member
- Posts: 5347
- Joined: Mon May 21, 2007 2:30 pm
Re: Unreal Tournament Editor problem
Blank? Wow, that means it doesn't initialise the log engine for some reason. But it has to initialise it before any viewports... That's really odd...
-
Leviro
- OldUnreal Member
- Posts: 5
- Joined: Sat Mar 13, 2010 9:49 am
Re: Unreal Tournament Editor problem
Ive tried the editor on the laptop and it works fine, so it must be something to do with my computer. The problem is I have no idea whats making the editor go wrong. Ive checked the log again, and this time its got loads of stuff, but im not quite shure what to look for, im guessing its the bunch of criticals at the end:
Critical: appError called:
Critical: Assertion failed: OwnerWindow [File:..\..\Window\Inc\Window.h] [Line: 1433]
Critical: Windows GetLastError: La operación se ha completado correctamente. (0)
Exit: Executing UObject::StaticShutdownAfterError
Exit: UGalaxyAudioSubsystem::ShutdownAfterError
Warning: glxStopOutput() failed: 6
Exit: Executing UWindowsClient::ShutdownAfterError
Critical: WCodeFrame::OnDestroy
Critical: WM_DESTROY
Critical: WWindow::WndProc
Critical: WWindow::StaticProc
Critical: WEditorFrame::OnClose
Critical: WEditorFrame::OnCommand
Critical: WM_HSCROLL
Critical: WWindow::WndProc
Critical: WWindow::StaticProc
Critical: DispatchMessage
Critical: 000A0382 273
Critical: MessagePump
Critical: MainLoop
Exit: Exiting.
Uninitialized: Name subsystem shut down
Hope that makes sense to you.
Critical: appError called:
Critical: Assertion failed: OwnerWindow [File:..\..\Window\Inc\Window.h] [Line: 1433]
Critical: Windows GetLastError: La operación se ha completado correctamente. (0)
Exit: Executing UObject::StaticShutdownAfterError
Exit: UGalaxyAudioSubsystem::ShutdownAfterError
Warning: glxStopOutput() failed: 6
Exit: Executing UWindowsClient::ShutdownAfterError
Critical: WCodeFrame::OnDestroy
Critical: WM_DESTROY
Critical: WWindow::WndProc
Critical: WWindow::StaticProc
Critical: WEditorFrame::OnClose
Critical: WEditorFrame::OnCommand
Critical: WM_HSCROLL
Critical: WWindow::WndProc
Critical: WWindow::StaticProc
Critical: DispatchMessage
Critical: 000A0382 273
Critical: MessagePump
Critical: MainLoop
Exit: Exiting.
Uninitialized: Name subsystem shut down
Hope that makes sense to you.
-
GreatEmerald
- OldUnreal Member
- Posts: 5347
- Joined: Mon May 21, 2007 2:30 pm
Re: Unreal Tournament Editor problem
Something with windows and frames... What's written a little above those criticals?
-
Leviro
- OldUnreal Member
- Posts: 5
- Joined: Sat Mar 13, 2010 9:49 am
Re: Unreal Tournament Editor problem
The rest of it is this:
Init: Unreal engine initialized
Log: Bound to Galaxy.dll
Init: Galaxy is using WinMM
Init: Galaxy initialized
Init: Transaction tracking system initialized
Log: Bound to Fire.dll
Log: Bound to IpDrv.dll
Log: Bound to UWeb.dll
Log: Bound to WinDrv.dll
Init: Mouse info: 6 10 1
Init: Client initialized
Log: Bound to Render.dll
Init: Lighting subsystem initialized
Init: Rendering initialized
Init: Editor engine initialized
Log: Startup time: 2.168632 seconds
Init: Input system initialized for U2Viewport0
Log: Opened viewport
Log: Bound to SoftDrv.dll
Init: Input system initialized for U2Viewport1
Log: Opened viewport
Init: Input system initialized for U2Viewport2
Log: Opened viewport
Init: Input system initialized for U2Viewport3
Log: Opened viewport
Init: Input system initialized for MeshViewer
Log: Opened viewport
Init: Input system initialized for TextureBrowser
Log: Opened viewport
Log: Closed viewport
Log: Closed viewport
Log: Closed viewport
Log: Closed viewport
Log: Missing name
Log: Closed viewport
Log: Missing name
Log: Closed viewport
Log: Missing name
Log: Missing name
Log: appRequestExit(0)
seem to be a lot of missing names and closed viewports, even though all i di was open the editor an move (or at least try) about.
Init: Unreal engine initialized
Log: Bound to Galaxy.dll
Init: Galaxy is using WinMM
Init: Galaxy initialized
Init: Transaction tracking system initialized
Log: Bound to Fire.dll
Log: Bound to IpDrv.dll
Log: Bound to UWeb.dll
Log: Bound to WinDrv.dll
Init: Mouse info: 6 10 1
Init: Client initialized
Log: Bound to Render.dll
Init: Lighting subsystem initialized
Init: Rendering initialized
Init: Editor engine initialized
Log: Startup time: 2.168632 seconds
Init: Input system initialized for U2Viewport0
Log: Opened viewport
Log: Bound to SoftDrv.dll
Init: Input system initialized for U2Viewport1
Log: Opened viewport
Init: Input system initialized for U2Viewport2
Log: Opened viewport
Init: Input system initialized for U2Viewport3
Log: Opened viewport
Init: Input system initialized for MeshViewer
Log: Opened viewport
Init: Input system initialized for TextureBrowser
Log: Opened viewport
Log: Closed viewport
Log: Closed viewport
Log: Closed viewport
Log: Closed viewport
Log: Missing name
Log: Closed viewport
Log: Missing name
Log: Closed viewport
Log: Missing name
Log: Missing name
Log: appRequestExit(0)
seem to be a lot of missing names and closed viewports, even though all i di was open the editor an move (or at least try) about.
-
GreatEmerald
- OldUnreal Member
- Posts: 5347
- Joined: Mon May 21, 2007 2:30 pm
Re: Unreal Tournament Editor problem
Just checked and everything above Critical: WEditorFrame::OnClose is normal for UT (it figures, nobody ever noticed that the editor has critical errors on exit :\ ). What the code below means I don't know, that's a developers trace. I guess Smirf could point that out, though.
