227g_26-29 Autoplay.unr Ed Problem

[Jet v4.3.5]

I got this problem when I installed 227g_26. I'm having the old "Can't find Autoplay.unr" problem. I did rename the UnrealEd.ini file and the Autoplay.unr files, but after reconfiguring the editor and trying it again, the same thing occured. It's more convenient for me if the button works so that I don't have to open Unreal and use the OPEN command to start a map, and I can't find any feasible advice for the problem.

[Jet v4.3.5]

I though I needed to bring this back up again. I installed 227g_29 on my older Unreal installation, and afterwords, I got the Autoplay.unr message, so I'm guessing that I'm having problems with builds 26 and up because of something in the patch versus my setup. I haven't tweaked anything. I did have an Unreal 227f install and a 227g install, but when I finally updated the 227f to the 227g_29, I got the Autoplay problem.

[[]KAOS[]Casey]

only thing I think this could possibly be because we've never touched this feature at all even through 227a unless you count it being unrealed 2 is the length of the full path to maps folder. What's the full path to it?

[Jet v4.3.5]

Maps folder?

D:\Programs\Unreal_Beta_Patch_Testing\Unreal\Maps

[[]KAOS[]Casey]

D:\Programs\Unreal_Beta_Patch_Testing\Unreal\Maps\autoplay.unr is 62 characters.. not sure if it qualifies for the length bug.

try shortening the "Unreal_Beta_Patch_Testing" to something like U227g

[Smirftsch]

anyone else with this problem? Seems to work fine for me without any problems.

[GreatEmerald]

No, it doesn't qualify for the bug, the limit is 80 characters.

[Jet v4.3.5]

I reinstalled Unreal and applied the 227g_29 patch. The game crashes at start. I un-reinstall the game and start it without patching it, then quit and install 227f. Then I install 227g_29 and it changes the resolution to whatever the default is at start, but it doesn't open a window or anything and appears to be doing nothing. I can try one more thing, but the install for it is questionable seeing as how it doesn't seem to work well with a fresh install of Unreal. My main 227g testing install still seems to be having the autoplay problem and something else weird popped up: I can't move forward, backward, or strafe, and it doesn't matter what keys are assigned to those movements. This could be due to my setup, but with the fresh install anomalies, that's generally almost solid, unless I can find a way to fix it so that it works correctly.

[Smirftsch]

the test archives should contain all necessary files to install it on a clean installation. But you need to take care that the uwindowfonts are in textures and that no unreal.ini is still existing. Let create Unreal a new one from default.ini
if still not working just post a log of this crash.

[Jet v4.3.5]

Nothing. Not even a log anymore. It's really acting strange, and even after doing everything you suggested, and with just about any combination of graphics/audio driver it still went to a blank, inactive screen.

[[]KAOS[]Casey]

sometimes it does that to me and I just hit alt+enter twice and it usually fixes it

[Jet v4.3.5]

BINGO! I got it! For some reason, and keep in mind that it's never done this for any other program just like this, but both my antivirus and antispyware kicked in at the same time which somehow caused a really long delay for startup. After waiting fifteen minutes or so, Unreal started, so it was on my end, as I suspected. Thanks for trying to help. It was mostly because of the newer online server changes from what I can tell.

This is a computer versus Unreal problem, now: whenever I start any installation of Unreal 1, even the new one, all of my binded keys work except the directional keys and crouch. I'm not too sure what's happening, and everything else seems to be working fine, but I did find this in the log several times:

Warning: ReadToken: Alphanumeric overflow

Also, this line is repeated several times also in the User.ini config. I don't know if I should delete it and let it make a new one or not, but here's the problem:

Fire",Alias="Fire")(Command="Button bFire | Fire",Alias="Fire")(Command="Button bFire |

I deleted User.ini and let Unreal make a new one. That worked perfectly.

[[]KAOS[]Casey]

Autoplay.unr fixed now too or just your movement and video?

Either way good to hear that's back to normal.

[Jet v4.3.5]

All of it is generally fixed in the new installation, except that I'm assuming my computer or Unreal is doing something screwy with my controls still. Whenever I change generally any of my controls in one session that had been working fine at that time and then restarted the game, the controls would no longer work, and I would have to quit and delete User.ini again and then I could restart the game, and as long as I didn't touch any of the keybindings, it wouldn't mess up the movement and crouch control.

[Smirftsch]

sounds like a known g29 glitch. g30 will be up soon.