AER is PARTIALLY COMPATIBLE with the Random Encounter Frequency (Awakening) component of Dain's Fixes. You must delete 'rand_forest_gxa.gda' and 'rand_plains_gxa.gda' from Dain's or ensure AER overwrites Dain's by loading after it.
As of V1.3, I've reworked the encounter system using uniquely-named encounter tables. So, other mods that attempt to change encounters will have no effect. ¯\_(ツ)_/¯
Happy to report everything seems to be working well. No repeating encounters and not stuck trying to exit any maps. Have seen over half a dozen random encounters I've never seen before, so I know the mod is working, although most use the same farm map, that's not your fault. All in all this is great work as usual.
almost every encounter in awakening is bugged to not let me transition. i have to debug out of the eara everytime. must be a conflict or this mod is insanly messy. also the included runscript does nothing
It sounds like there's a severe incompatibility somewhere in your mod list, or even your install. (I'd guess the latter - even if the map transitions are bugged--known issue--then the runscript should still work!) :/ I'd recommend uninstalling this mod (you should be able do so with no consequences) and use "runscript zz_rxa_debug" to trigger encounters instead.
I don't want to point fingers at this mod without first asking if anyone else has experienced something similar, but I'm facing a very odd issue in Awakening. Basically, random encounters don't have working exits. At the places where the exits SHOULD be, the map shows a regular "pin" (one of the little X marks) as opposed to the transition icon. Mousing over it declares it to be a world map exit, but right clicking on it does nothing. Walking into it produces the expected "gather your party and venture forth" box, but clicking "yes" closes said box WITHOUT bringing up the world map; you're just left standing there in the random encounter location. This has happened for both Lillith the merchant and the random clearing full of sylvans (one of them charred). In order to get out of either area, I was forced to open the console and use runscript zz_rxa_debug to teleport myself to an area with a working exit (e.g. Forlorn Cove). I can't find any reference to a vanilla bug of this description, and I'm 99% sure that I'm not using anything else that changes Awakening encounters, leading me back here. Does anyone have any idea what this issue could be?
EDIT - I apologize that I somehow missed this line before posting: "On occasion you will be unable to leave an encounter map. It only happened for me on my older computer, not my new one, so I suspect it's related to engine strain / RAM limitations. As it seems to be a compounding issue, I've included a runscript to get your party travelling again if saving/reloading doesn't fix it."
This actually increases my suspicion that this mod is the source of the issue. But saving/reloading - which I tried - has never fixed it, and I highly doubt that it's caused by a system UNDERperforming. My current PC has 32 gigs of RAM (and yes, I made sure that my DAO install is LAA-patched) and probably the weakest component I have is my RTX 3070 GPU. That should be more than enough muscle for DAO. And as I said, this has happened in literally EVERY random encounter, including my first one, so I wouldn't even describe the issue as "compounding." At least now I know about the included workaround that I stupidly missed originally. So I really appreciate that, and I'll just try to make do using it.
I also have a good PC but the problem is the shitty game engine. I play with Dains Fixes and in some intensive battles i got massive delays of 2 to 3 seconds to apply effects or damage. It must be the same with this mod. It's extremely cpu bound and not greatly optimized(due to how old the game is obviously)
This is an unrelated question but. I've been having an issue ever since I've gotten a new pc where the screen will turn grey or black during cutscenes. Either a few objects will show up and sometimes the characters but then it will turn grey again. Do you have any idea what to do or where to go for information?
Uh, that is weird. My first instinct is to check if your game is LAA / 4GB patched. You could also try running it in compatibility mode for Windows 7. I've also heard people have luck running the game in DirectX 9, or on a single processor (which I don't know how to do offhand, you'd probably have more luck with Google). Otherwise, the folks on either the DAO Reddit or modding Discord might know something.
The trigger conditions didn't change. Unfortunately, I am out of town for the week so my help is limited, but: Are you getting any random encounters at all? Did you update to the newest version, and if so, did you install all the new files?
Nice mod. Seems to be the only one that actually fixes the Velanna's Exile encounter. Unfortunately causes a couple new bugs. Details posted in the bugs section.
Hey, thanks for the mod! I didn't see it mentioned anywhere, (unless this's what you meant by cleaning up the travel script) but this actually made my games load times in Awakening SIGNIFICANTLY faster, with less of a delay before and after the swords appear for an encounter, so I appreciate that.
38 comments
AER is NOT COMPATIBLE with Lemming's More Random Encounters for Awakening.
As of V1.3, I've reworked the encounter system using uniquely-named encounter tables. So, other mods that attempt to change encounters will have no effect. ¯\_(ツ)_/¯AER is PARTIALLY COMPATIBLE with the Random Encounter Frequency (Awakening) component of Dain's Fixes. You must delete 'rand_forest_gxa.gda' and 'rand_plains_gxa.gda' from Dain's or ensure AER overwrites Dain's by loading after it.
I'd recommend uninstalling this mod (you should be able do so with no consequences) and use "runscript zz_rxa_debug" to trigger encounters instead.
EDIT - I apologize that I somehow missed this line before posting: "On occasion you will be unable to leave an encounter map. It only happened for me on my older computer, not my new one, so I suspect it's related to engine strain / RAM limitations. As it seems to be a compounding issue, I've included a runscript to get your party travelling again if saving/reloading doesn't fix it."
This actually increases my suspicion that this mod is the source of the issue. But saving/reloading - which I tried - has never fixed it, and I highly doubt that it's caused by a system UNDERperforming. My current PC has 32 gigs of RAM (and yes, I made sure that my DAO install is LAA-patched) and probably the weakest component I have is my RTX 3070 GPU. That should be more than enough muscle for DAO. And as I said, this has happened in literally EVERY random encounter, including my first one, so I wouldn't even describe the issue as "compounding." At least now I know about the included workaround that I stupidly missed originally. So I really appreciate that, and I'll just try to make do using it.
Otherwise, the folks on either the DAO Reddit or modding Discord might know something.
Are you getting any random encounters at all?
Did you update to the newest version, and if so, did you install all the new files?