![]() The fix that went live last week has not propagated through the weekly maintenance (if it ever worked at all). Not sure why this was moved GD but i’m going to assume it was a mistake Only 3/4 spawning once every reset for each layer. If it’s from the last Green Dragon killed and one dragon continues to not spawn, then we might never get a second wave of Green Dragon spawns. The other reason why this is significant is we don’t yet know if the respawn for Green Dragons is from the first Green Dragon killed or the Last (third/fourth). This bug could also not be limited to just my server but could be affecting all servers on all layers. The side-effect of this is: some locations will have a second dragon spawn after the first is killed, and the re-issue includes the randomization, so. After fixing it, we decided that it was better to re-issue the command to make sure all locations got at least one dragon. Reason 2 is bad because it potentially means that both Layer 1 and/or Layer 2 will continue to not spawn four Green Dragons after this Tuesdays maintenance. We had a bug on rollout that caused some locations to have no dragons. Reason 1 is bad because it means the dragons are not synced properly. The bug was never fixed in the first place.Layer 2 was copied from Tuesdays maintenance which originally had the Hinterlands no spawn bug.Hinterlands inherited layer 1 spawn timer despite all the other layer 2s spawning.This is well outside the normal spawn window for a “reset” spawn. Also note that due to a bug, the game will now enter an infinite loadscreen if you play whilst connected to PSN. It has been now been 48 hours without a Hinterlands layer 2 Green Dragon spawn. The Green Dragon on Hinterlands layer 2 did not spawn with all the other Green Dragons on layer 2 after layering was implemented. This was then fixed by Devs force spawning all the dragons again. The ritual was first developed by cultists of Tiamat. The ritual mutates the embryo inside, and what hatches from the egg is one of these beasts. You could also try and delete the majesty2 folder that is located in "my documents" c:/users/name/mydocuments (note, path is for win7), don't forget to make a backup of "profiles" folder in that.My server Arugal (OCE) originally had 3/4 Green Dragons spawn last week where the Hinterlands boss didn’t spawn. Dragonspawn are weird mutants created by the application of an eldricht ritual to an unhatched dragon egg. Maybe the game is trying to start up in an unsupported resolution? ![]() ![]() Use the controlpanel of your gfx-card to set up different options for that game only (I have forced Vsync turned on myself for this game). Validate the integrity of the local game cache. I'll throw out a few ideas to help brainstorm the issue. I mean, I don't want to buy Majesty 2 Collection to play the game, because I don't want to waste money doing so and find myself going through the same issue. When I tried to run it and the map editor, from the SteamApps folder its in, I got an Application Error message, with it stating the error under code 0xc000007b.Īnnoying thing is, when I tried to see if anyone could help me, I had this idiot who was truly unhelpful, suggested I buy a pirated copy, and then rather *helpfully* suggested I watched a playthrough. I mean, it showed it "Running" in my Library for a brief few moments, then nothing. After I got it back, I found that no matter how many times I re-installed this game, it wouldn't run. I was able to run this on my computer without problems, before I had a software issue with my OS that left me getting my computer being checked up and repaired. Originally posted by FireDrake85:I found myself having a rather serious issue with running this game myself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |