Nope! I spent ages trying to phrase that right, so read it again: it says cells BEYOND -6464. -64safe range.

Everyone who cares about this and has a twitter account needs to tweet - and if you don't have one then make one just for this! Send tweets to @BGS_devs, @Bethblog and @DCDeacon quoting the hashtag #SkyrimWorldspaceBug

Twitter is a mass-communication tool: that's its point so if Bethesda use Twitter (and they do) they can hardly complain if it's used for what it's designed for. If they've got a decent twitter client I think they should be able to filter out the #SkyrimWorldspaceBug hashtag to see everything else separately.

Seriously: the squeaky wheel gets the grease. Make a noise and it may be fixed. Be quietly polite and it won't.

If I understand this correctly, the problem is the game engine itself which seems to contain the bug.

I am no programmer, so forgive my ignorance, but is it completely and utterly out of the question for someone to 'look under the hood' of the game engine, identify the problem and come up with a fix/patch?
In other words - will this only be solved if Bethesda decides to live up to it's claims of wanting to support modders and actually release a fix themselves?

It would be extremely difficult for someone else to do so, though surely not impossible. The problem is there would be limitations, third parties cant patch the game and doing so might be illegal, cause other problems and so forth. Its a good idea to try to narrow down the problem though.

Echoing the clarion cry of Morcroft Darkes, might even be worth adding to a sig

"Everyone who cares about this and has a twitter account needs to tweet - and if you don't have one then make one just for this! Send tweets to @BGS_devs, @Bethblog and @DCDeacon quoting the hashtag #SkyrimWorldspaceBug"

I think that is beyond what third parties can do. The clever peeps can work around almost any CK issue, and can poke values in for particular uses - such as SKSE, but the actual code of the game is, I think, difficult and dangerous to modify. Besides which, you're asking every gamer to patch their executable to allow them to play our mods. Come to that, if Steam workshop ever reaches its full potential, there's no way we can patch the executable on consoles.

I plan on adding a call on our ModDB page soon, hopefully today and else tomorrow. I'll first have to go through it with one or two other MERP team leaders though.


It's theoretically possible I suppose, but a great amount of work to reverse engineer the code where the bug might be found. It would require the best programmers the mod community has to invest major time in fixing it, while success isn't even guaranteed. @others, it could perhaps be in the form of a DLL injection using the SKSE rather than a real patch.

Oh God, I really hope this will get fixed somehow.

Many thanks to Maegfaer for raising awareness of this terrible bug, and for not giving up on MERP in Skyrim.

I really hope that beth accnowledge this error soon; beside the NavMesh-Bug this is one of the worst: it affects a lot of modders because the engine set an limitation of the size of the world space and set so an limit to the moddability of the game itself. this would affect many big projects if there is no solution.

@Dagoroth
Maybe there is a way to fix it, and as i know some great modder from the skse-team or someone else will find a way; even more since the error seems to affect only the x-axis (or was it the y-axis; i don't know); but we can't be sure and the best way would be if this bug is fixed in the engine itself.

I really hope that someone or beth itself will fix this bug; because since the NavMesh-Bug seems to be fixed in the future, this is by far the worst bug now.

It's the X axis. It does seem arbitrary that the northernmost tip of Atmora wouldn't be a problem but the game starts glitching out if you go too far west or east.

Come to think of it, we haven't tested the Z axis. This could affect the "travel to Australia" blackreach expansion mod I'm planning.
(joke)

I'm pretty sure the Z axis limit is close to the top of the Throat of the World. The base sea level in Skyrim is much further down (in the negative zone) than it was in further games to accommodate the height of the mountains.

I tested the Z-axis, my Middle Earth map has some pretty extreme height differences. Z-axis doesn't matter, it's just the X-axis.

I could understand if it was both the x-axis and the y-axis, but when even the z-axis doesn't have problems, and the y-axis have no problems, why only the x-axis?

Ive been very high up in Mesogea. In L3dt its in the 1400 metre range at the highest point.

Oh please Bethesda. Fix this bug!
It has the potential to single handedly kill off some of the best player modding ever made.

Maybe we should convert MERP and put it on its side so it will extend into the Y and Z axes...

Of course, the moutaintops might suddenly become a problem.

I sent a message to Gstaff a while back (just before Morcroft said not to spam PMs) and I got a reply:


Not quite an acknowledgement from a game dev, but it does seem like it will be put on the radar. Should I reply again to thank him for replying?

I should probably post my original message:


I hope I didn't come off as too snooty :V

I think that's fine - and a very good start! Always worth replying to a reply, I'd say: just say thanks and we hope for an update as soon as possible.

Tiny bit snooty, but I wouldn't be offended by it! And a few PMs isn't spamming: asking everyone on the MERP forum to PM would be spamming.

heh I wanted to pm a dev as well for reporting bugs, but I fear that would be understood as harassment and could lead to no bugfixing at all on their part. but maybe a famous modder can do that without coming off as a spammer.

I think it was a perfect PM. Glad we got a reply. What do you guys think, should MERP still put that twitter call on the ModDB page?

I think it should be done, yes. If the Devs see how many people are affected then they are more likely to put this higher up the "to do" list.

I agree - lets see what Twitter can do. In a way this is potentially useful information for gamesas as to what sort of interest there is in big mods like MERP.

I think the MERP team should definitely arrange a call to arms via Twitter.
Perhaps put up a standardised tweet on the ModDb for all people to use. Something polite, but still making it clear how important this is.

Hoping any new news or any correspondence with Bethesda will get posted here for people to see.

twitter yes. it's MERP team, they can't be ignored, they're too good!

Could I just ask - when you say "a while back", when exactly was that?
And also, precisely who is Gstaff?

The time stamp is 16 February 2012 - 11:19 PM, in GMT+1. Two days ago basically.

And from what I know, Gstaff is like the ambassador of Bethesda to the modding community. Forum administrator without being a part of the development team, although he is in communication with them.

Bethesda I usually love you but when I come across this bug. I get mad. Real mad.