First off, I'm not a big fan of text responses, because 90% of all communication is non verbal, and words are easily misinterpreted and what not.
What I'm about to say isn't perhaps going to be received well and if that's the case too bad. It's one's own choice to interpret things how they wish.
Others "choose" to interpret what I say how they wish. When they do that, it often doesn't align with my intents--others don't get to decide what my intentions mean, and this applies in reverse as well.
I stated what I'd do right off the bat based on provided info in order to convey that I'd have a clean slate to start with in order to resolve any issues. If the problem(s) immediately resolve(s), then I know for certain that the files were the culprit.
As far as a particular feature in Abyss, this wasn't mentioned until later... Then when slipslide did, they choose to say that Abyss as a whole has something wrong with it--they weren't specific. There are going to be some features that work at times and others that do not. This is fairly common with any updates that occur to the client.
Me conceited? No, it's called being sure of one's self. I'm prepared to admit I'm wrong-which I admit to a fault later on in my quoting, but this was based on good faith of how others acted and the info that they provided--or rather lack of it.
I admit I don't use that feature that people are having issues with, but I don't use it because often times it only worked when it wanted to and any times I've used it in the past it has failed. Had this been said initially, then all of this could've been avoided.
That being said, I only use features that I know work and have shared these in past posts-disabled ones that don't.
A little history: This is why I coded into the script for Tiara to turn a lot of features off in the past, and even when the latest V C++ updates I had to disable features based on what I saw others doing--what worked and what didn't.
There's a common saying, "Everybody lies..." Whether this be of intention or by omission, this is true and based on experiences in many fields--many have seen this to be true. This is what's happened here.
So I'm providing an outline as follows:
Any idea when I can expect the new version of abyss to work on my computer? I'm running Windows 10 Pro
I responded to this based on the information provided to me at the time. I also went back and looked at past posts. =/
Then I responded to the next post by Drakelegion:
I used power patcher to try to fix a problem before, it had no luck. I redownloaded mabinogi on the 7th(7 days ago), and the new version of abyss did not work at that point in time, causing the errors I stated. I re-installed the just prior to that version of abyss, and now it works fine.
Its not about it worked X long ago. The newest version of abyss doesn't work, the one prior to it continues to work as well as it used to.
I hope that clarifies where I am at enough that we can move on to things I have not tried.
At this point I was still going on provided information... This was after Playtime had responded.
I'm stuck on the white screen before the log in screen with just Abyss. I went back to old version, and I'm having the same problem. Anyone else having the same issue?
I avoided this post because I was already dealing with 2 people already. Ah, the beauty of choice. I chose to deal with that later, and now that may no longer be necessary. Then slipslide chose to respond to it thinking their issues were related perhaps?
Then I responded to slipslide:
Well, I've followed all of the above advice since my post on the previous page.
If I run the game with no mods, it runs perfectly (except if I hit a cutscene, then I jam)
If I run it with the previous version of Abyss added in, it runs perfectly.
If I run it with the new version of Abyss added in, it takes forever to launch, and then stutters every quarter second and is unplayable.
Yes, I cleaned up all old files. Heck, I even made a second Mabinogi installation to work with to make sure. The only modification I'm using IS Abyss. There's a bug somewhere in the new coding, so I can't try out the new features. As long as the old one still works, I'm not too worried.
I'm running Windows 10 Home, btw. Not Pro.
slipslide then continued on with responding to sounggi. No new information was discovered at this time. I covered standard procedures that I do based on these facts and since there were no specific details revealed yet, other than cutscenes... I addressed that.
Then I got a response from Drakelegion:
Alrighty then, my version of win10, like most others, is upgraded from win 7, I am running an 8-Core, 3.4GHz, 64-bit processor. I have 8 GB of RAM on one stick with room for more(in case that has a chance of mattering), and an nVidia GeForce 750 Ti Graphics card from EVGA. My HDD is 3TB, and I access the last TB of it using some drive powertool that came with my MSI motherboard.
If I missed any information you need to know in order to help me, please let me know. I am a tech guy, but am not very familiar with the ins and outs of modding mabi, only how to implement what is on the forums(read instructions and follow them).
I apologize for getting snippy, I am not used to having things not work right the first time, and being babied must have set me off.
I explained further... based on the provided information so far, and even offered to help personally--going so far as PMs.
Then slipslide posted:
Nope. Doesn't matter if I disable EVERYTHING on Abyss! As long as I'm using the new Abyss .ini and .dll files, it's a stutter-load failure. As soon as I either switch back to the Mabinogi ijl15.dll file or the one from the previous Abyss version, everything's perfect.
The fault is the new ijl15.dll file, or how the new abyss.ini calls the functions from it. I can say that with 100 percent certainty.
I responded appropriately based on the info provided so far. Interesting to note, still no new information that was relevant was provided yet... So, knowing this I responded based on the "knowing" that if it's dll related, then this as a factor needed to be eliminated. Instead of following this thought process, I was criticized for it. Interesting indeed.
Then Drakelegion provided some new info:
Found my problem:
The window resize/position mod.
When I disabled this mod, mabi runs just fine.
EDIT:
To be more specific, when I had the window size/position hook enabled, mabinogi would start as a background process, as it always does, but it would never switch to the list of apps, which it does when the window shows up.
Interesting indeed. So at that point it was discovered it wasn't Abyss specifically overall, but a feature within it. Well this makes sense, hence my response thereafter. I was still responding to another post after I'd replied.
Okay, I'll humor you. In fact, I'll do you one better; I'll use power patcher to repull ALL the files, since I'm not busy right now. I'm telling you, there's a bug in the new Abyss that does not let it play nice with a mostly unmodified client... such as the one I was using, which had NEVER USED POWERPATCHER at all. I was still using the original Nexon launcher to play the game (not using the Steam version). Literally, the only thing I had done to my game was stick the contents of Abyss into it, and modify the abyss configuration to remove some of the features I didn't want.
Before doing this, I messed with my settings some more. No matter what I did, the game would launch with the original dll and the old abyss dll, and the new abyss dll would either cause stuttering or claim I didn't have the DLL and needed to reinstall.
There is most definitely a small coding error, and it only affects a certain combo of OS/install locations/launchers used.
But, never mind the person who's been recoding stuff since Windows 95 first edition, and doesn't feel like pulling files apart to see what makes them tick, and just wants to sit back and enjoy a game as a user for once
I proceeded to set slipslide straight about how PP works and this was going on while other posts were being made still because I got the usual new posts have appeared while typing thing when I went to submit it (it was 3 more posts btw)... I submitted it anyway, and this was where I screwed up--I admit. =/ This was after Drakelegion had posted the first piece of relevant info, and then noting that ╰( ´◔ ω ◔ `)╯ and sounggi had responded. While I was attempting to submit I'd been acting on good faith.
Then sounggi responded:
My resizing is already disabled but I get stuck on white screen before log in screen with Abyss. What reason might that be?
Interesting indeed... A new piece to the puzzle, but the thing is even though the problems are related to Abyss possibly, they're not one and the same.
Then slipslide replied:
When you disabled it - did you comment out those lines in the settings file, delete those lines, or add a zero for the on/off line? If I'm still having trouble when I finish patching, I want to try the same fix.
Their 2 problems might be related after all, but do note, that their problems though similar didn't have this info before when I responded. Interesting indeed. I responded based on the provided info initially, but now it was obvious that 2 problems that people were having might be related, and sounggi was still unanswered by me.
The following ╰( ´◔ ω ◔ `)╯ was attempting to help, but based on past posts, I acted accordingly (based on the info provided).
Then ╰( ´◔ ω ◔ `)╯ posted and I responded:
Yep. Any value other than 0 seems to keep Mabi from running for me, too. What a nightmare.
My response was an attempt to lighten the mood based on past posts of theirs, and let's be honest here... A feature being broken/not working isn't really the end of the world is it? That is how I "chose" to see it and responded accordingly. Still it's interesting to note that, Now the 2 main pieces to the overall problem have now been revealed. This was after the fact of my initial responses based on provided info. Indeed... If one feature isn't working doesn't mean the whole "program" is broken. Blade will get to it when he gets to it. So this means... wait for it... he'll get to it when he gets to it. Not really that darn hard to understand is it? Geez.
I felt it was too darn serious, so yeah, I responded to what I felt at the time was appropriate.
Then ╰( ´◔ ω ◔ `)╯ posted:
No. I use it for playing borderless.
Which of course I didn't respond to because at that time I'd stepped away again. Upon seeing it, I was surprised. I thought, ok, so he was serious--he uses that feature.
Then slipslide posted:
Draconis, I'll be giving it another shot once the download is done, with different solutions on the window resize/position mod, as two other users have mentioned it since I started the full redownload.
I still need to know how they disabled it, whether it was removing the lines, commenting them out, or zeroing the entry. It seems to be the only fix that I haven't fully explored.
That said, you've insisted over and over again that the problem was with my files. I've already proved it's not, and yet I'm still doing a full redownload. Why? Because you INSIST that it's my files, and that's all you want to go on. Yet, now the resize/position settings have been called out, with two users complaining about the same problems I had mentioning that was the fix. If this really is the fix, and if you would have stopped for a moment and maybe had me go down the list item by item, making sure I was disabling them properly, I could have avoided a full redownload.
You committed the first sin of tech support; working off a script and not listening to the end users.
Really?!?! Really?!?! Really.... Apparently...
I acted based on info that you provided, and the fault lies with you by a "lie", an omission on your part. What a load of crap. You're blaming me for your short comings in failing to provide me with info that was needed. I had to figure this out on my own by piecing together all that had transpired. It's not like you offered the info initially--that part is evident and obvious. Yes, I'll admit I worked off a "script", if that's what "you" want to call it, but it's you who "chooses" to see it that way. The only reason you're attacking me saying I "committed a sin" is because you chose to and failed to provide all relevant info. I shouldn't have revealed at all that I have past tech support experience, because you chose to make it personal and attack me later with it. The real "sin" here is obvious that you lied by omission, and are trying to cover up your actions or lack of. I felt I acted very appropriately up until now based on info that you provided. Stop blaming your problems on others, it's a well known fact that Abyss has had issues with the particular feature that is spoken of, if one would take the time to actually read past posts. Had you actually done as I suggested and done the process of elimination, then you would have found the exact problem, without needing to post all that which you did. Then, you could've posted your findings, and then this would've helped the community instead of what we're seeing.
Then you later confirm what I'd been saying all along. Wow... just wow... Never mind that you also failed to mention that you'd been using 2 PCs the whole time.
Okay, here's what happened: I used two computers, as I've been doing all along, and on one, I redownloaded the game through normal means, and on the other, I used the power patcher. That way, there'd be something to work off of.
The game downloaded through normal means would not work with the newest Abyss patch no matter what, even with the resize lines deleted. However, the game downloaded through the power patcher DID work, once those lines were deleted.
Funny thing, though... there's a LOT more files in the power patcher one; files that are most definitely steam related, and some extra Microsoft files as well. Something tells me there are things added to the base client via powerpatcher that are being called upon by Abyss.
In any case, I'm running the powerpatcher version now on this computer, and on the other, I'm on the old abyss.
As far a my response to this, well... here it is and trust me, I'm holding back:
Yep. He pretty much went from "I like to help people" to "You're wrong, I'm right".
Conceit can do some nasty things to people.
For the record, zero'd it. But if you removed it from the file or commented, the default should be zero, too.
Try disabling the new features, since some of them are enabled by default, and you're saying that only the updated abyss messes with your game.
Forgot you tried disabling everything already.
Hmmm, that's like the pot calling the kettle black isn't it? One is incapable of seeing flaws in others that one doesn't have or have had or experienced themselves. This is because one doesn't have the knowledge of these things due to lack of experience. I'm not conceited, but I am sure of myself and what I do know, and it will change as things change. The only reason I'm even responding is to "enlighten" you to the fact that you're an experienced member of the community, and you clearly haven't learned a darn thing. Your perception isn't gospel--I really don't care what others think of me, but if you're going to go around attacking my character and slandering my name... I'm sorry, but I'm going to defend myself and have a right and responsibility to do so. I take this rather personally--because you crossed that line and made it personal. We're both human and that means we make mistakes. Stop thinking your crap doesn't stink, because everyone's does. =/ You of all people I never expected this from. Really? Jeebus.
I went by intentions that I read based on the actions and words conveyed before I responded and thought this out for quite some time. I do have a right to defend myself and to be upset--it's called righteous anger. I didn't say really all of what I've been thinking, and perhaps that's for the best. However, when I spoke to another... They pretty much told me this: People will do what they're going to do, and the fact is this. If you take your time to help them, and they don't appreciate it or they purposely try to leech off of you all the time... Then perhaps maybe you need to stop helping them. I feel those are very wise words, and I may be acting on them--because who needs this headache. =/
Think what you want, you will anyway. However, this is choice to limit one's self. Frustrated or not, when it gets to be too much I step away, and choose to revert to square one as necessary.
There's so much that I'm not even saying here, and because of one simple thing. I'd be going on for hours trying to explain myself. Sorry, I don't have that kind of time (no one does). I obviously give a darn or I wouldn't take the time to respond.
I've honestly better things to do than to bandy words back and forth trying to get others to see the big picture.
Small wonder that many of the more seasoned veterans have said to heck with this; I've been putting up with it for over a year now--and already I've had my fill.
@Blade, Playtime and the Professor,
Thank you for all that you do and continue to do.
@Shaggy,
Don't worry about Tiara, I've got that covered, but beyond that I think it's time for a break otherwise.