Holy cow. 800+ land tears fixed! I noticed a land tear in the latest version of Better Cities Cheydinhal between cells 28,21 and 29,21 and couldn't figure out what the problem was since that was the only mod that affected those two cells. This just fixed it magically! ENDORSED!
I had something like that happen when I tried to use a modified version of a DLC.esp that I had mad with on my old Disc installation with my new GOG installation. I had to make the mod again on the DLC .esp that had come with the GOG version to use land magic. Something different in the packaging of the DLC.esp between the old disc version and the GOG version. Have you god a modified DLC.esp on your installation?
Guys put this program into Compatibility mode for windows 7. And run as administrator. It will work so much better and even fix floating trees if you're not using Unnoficial Patches
I had an issue where landmagic 32 bit would encounter and unknown exception on processing my load order; specifically tamriel.esp. While experimenting , the 64 bit version of land magic did not get this error and all else seemed to go go well. i am Using Mod Organizer 1 as my mod manager for oblivion and wrye bash. Mod Organizer can not launch Landmagic64. So at this point i made the 32 bit version of landmagic LAA (large address aware) by using the 4Ggb patcher and now the 32 bit version of land magic works flawlessly on my load order including many twmp esps; valendwood , anequina, elswere palletine... . i am happy with it. BTW i am still running windows 7 professional 64 a 12 year old laptop
This mod can fix some minor land tears, but it can also cause problems too - particularly with patches. For example, the Golden Arrow Archery Shop when used with Unique Landscapes is buried in the hills and inaccessible, but there's a UL patch to fix that which works perfectly. When I ran Land Magic, it reversed those changes and made the shop inaccessible again. I semi-fixed the problem by moving the UL patch below the land magic esp, which put the shop above ground again, but it still left a land tear that wasn't there before. Land Magic also breaks the Bleaker's Way Revamp / HESU Apple Springs patch; that patch removes land tears, and the use of Land Magic actually puts them back! And those are only two I've discovered; I'm sure there are many more.
Land Magic should be used with extreme discretion; it can potentially cause as many problems as it fixes. I stopped using it permanently.
Load order is often important with using this when edited cell overlap rather than just bordering each other. In such a case Generally you will want the lower elevation mod loading after the higher elevation mod. Sometimes it just will not be able to reconcile mod elevations when they are overlaping
Land Magic has to go at the end of the load order, right above bashed patch, so it overrides any changes patches make when they both touch the same area. It's a seriously dangerous tool to use if you have a lot of mods & patches. But people can always try it, since it puts all its changes in an esp and doesn't make any permanent changes. If you notice it's reversing patch landscape changes, just delete the Land Magic esp. But I'll never use it again since it caused some serious problems.
Either that of the 64 bit version. I have three installations of Obivion, how is it going to know which one to patch? I don't think it is finding any of them. Now (three months later) it does start, I click the button and get this:
Program Exception:Unknown mod type(not .esm/.esp)!
I am using that one, the 32 bit: LandMagic.exe on a 64 bit Windows 10 machine not using the LandMagic_x64.exe and have not tested it.
Edit: Just tested it, no crash.
You problem may be the 3 installations, of it may be a type of plugin it cannot handle as "Program Exception:Unknown mod type(not .esm/.esp)!" would make me suspect. When I first set up my current GOG installation I had a problem with Land Magic crashing when it reached a certain plug in. I use an edited DLCvilelair.esp when not using and evilish character, and rather than making an edit from the one in the GOG installation, I imported the edited one from my old retail disk installation of my old computer and land magic would choke on it. It worked fine when I instated edited a copy of the new GOG DLCvilelair.esp. However, in my case it would start up, and then later abort when it reached that imported plugin.
Re mod organiser 2. you have to list land magic in the executables tab under tools, then add it. make sure land magic exe is in the data folder then look for it after clicking the + sign in the executables tab. Then run it from the drop down tab which includes options such as obse, teslodgen etc. same with wrye bash, every mod profile has to be done this way. works for me.
Unfortunately, doesn't seem to work with a Mod Organizer 2 setup. upon clicking Land Magic It says Oblivion is not loading first. I'm guessing because MO2 doesn't manage the Oblivion ESM. Guess I can't use.. This was made 11 years ago so MO2 wasn't around so the tool can't recognize it. But I sure am no Expert. All I know is it won't work for me. Seems I can't use the whole Landscapes Compilation. May try individual ESPs if I can find recommendations for the better ones. Probably because of the Virtual System MO2 employs. Might try putting Land Magic in Directory and blow up my game.
cannot get it to work on a GOG windows 10/ TESMM installation outside program files tried both the 64 bit and the regular version it starts, runs through the vanilla and DLC ESM and ESPs then quits Tried the windows 10 compatiblity tools and run as administrator All the same result had no trouble running it before on an windows XP / OBMM installation suspecting something to do with the mod manager because in runs at far as the regular game plugins
This is a shot in the dark, but could it perhaps be a file date issue on the plugins?
I remember having problems running TES4LODGen before, because the file dates on my plugins were somehow set weirdly. I suspect not all esms loaded before the esps, or maybe some dates were too close together. BOSS and Wrye Bash didn't complain, but LODGen refused to work. Just using BOSS didn't fix it; I had to use the redate functionality in Wrye Bash.
I can't recall if I've ever had the same issue with Land Magic, but redating the plugins could still be worth a try. Hopefully TESMM has that functionality.
It was choking on my edited version of VileLair.DLC Maybe my edits (to de-evil it a bit and use it as a spy lair instead of a Dark Brotherhood lair for my current good charactor {who has slaughter the DB}) scrambled its date record or introduced some spurious Master record. What is strange is that choke on it it on Windows 10/ TESMM installation but not on the old Windows XP / OBMM installation
It was hard to catch because it would not give an error message, just quit when it loaded VileLair
94 comments
Have you god a modified DLC.esp on your installation?
Will this make the x64 version work?
specifically tamriel.esp.
While experimenting , the 64 bit version of land magic did not get this error and all else seemed to go go well. i am Using Mod Organizer 1 as my mod manager for oblivion and wrye bash.
Mod Organizer can not launch Landmagic64. So at this point i made the 32 bit version of landmagic LAA (large address aware) by using the 4Ggb patcher and now the 32 bit version of land magic works flawlessly on my load order including many twmp esps; valendwood , anequina, elswere palletine... . i am happy with it.
BTW i am still running windows 7 professional 64 a 12 year old laptop
Land Magic should be used with extreme discretion; it can potentially cause as many problems as it fixes. I stopped using it permanently.
Sometimes it just will not be able to reconcile mod elevations when they are overlaping
LandMagic.exe
to start?
Program Exception:Unknown mod type(not .esm/.esp)!
I think this program is not for me.
LandMagic.exe
on a 64 bit Windows 10 machine
not using the LandMagic_x64.exe and have not tested it.
Edit: Just tested it, no crash.
You problem may be the 3 installations, of it may be a type of plugin it cannot handle as "Program Exception:Unknown mod type(not .esm/.esp)!" would make me suspect.
When I first set up my current GOG installation I had a problem with Land Magic crashing when it reached a certain plug in. I use an edited DLCvilelair.esp when not using and evilish character, and rather than making an edit from the one in the GOG installation, I imported the edited one from my old retail disk installation of my old computer and land magic would choke on it. It worked fine when I instated edited a copy of the new GOG DLCvilelair.esp. However, in my case it would start up, and then later abort when it reached that imported plugin.
Probably because of the Virtual System MO2 employs. Might try putting Land Magic in Directory and blow up my game.
Or maybe check your load order to see if any file, maybe even a ghosted one, is loading before Oblivion.esm
tried both the 64 bit and the regular version
it starts, runs through the vanilla and DLC ESM and ESPs then quits
Tried the windows 10 compatiblity tools and run as administrator
All the same result
had no trouble running it before on an windows XP / OBMM installation
suspecting something to do with the mod manager because in runs at far as the regular game plugins
I remember having problems running TES4LODGen before, because the file dates on my plugins were somehow set weirdly. I suspect not all esms loaded before the esps, or maybe some dates were too close together. BOSS and Wrye Bash didn't complain, but LODGen refused to work. Just using BOSS didn't fix it; I had to use the redate functionality in Wrye Bash.
I can't recall if I've ever had the same issue with Land Magic, but redating the plugins could still be worth a try. Hopefully TESMM has that functionality.
Maybe my edits (to de-evil it a bit and use it as a spy lair instead of a Dark Brotherhood lair for my current good charactor {who has slaughter the DB}) scrambled its date record or introduced some spurious Master record.
What is strange is that choke on it it on Windows 10/ TESMM installation but not on the old Windows XP / OBMM installation
It was hard to catch because it would not give an error message, just quit when it loaded VileLair