- Joined
- Jan 31, 2005
- Messages
- 11,859
- Reaction score
- 586
- Points
- 113
- Location
- Australia
- Website
- www.mmobugs.com
Please be sure you are using MMOLoader.exe if you wish to use any MMOBugs private plugin.
This thread is for feedback concerning the latest release. Simply reply to this thread with the information requested below to report any problems or concerns relating to this release.
For a list of plugin commands please read our MacroQuest2 FAQ
This release is based on MQ2-20151118.
_______________________________________________________________
Having a problem?
If you are reporting an issue with this compile please use the Send Debug Report from MMOLoader. You can also post here with any general issue, or even to just let me know you sent a report. If you expect a personal response, in email or this thread, then provide feedback in the comment box provided in the debug report, and provide an email address. If not, then I will look at the report and make any decisions I need to based on that, but will NOT respond to you personally in email or this thread.
You're welcome to email me at htwmmo@gmail.com for any reason. Please state your mmobugs forums user name in the email so I know who to contact on forums if needed.
If you want some 1:1 support, we can try to arrange an appropriate time window to use Skype, or RDP support invitation, or TeamViewer for me to try to help with your issue. I am also willing to log into your EQ character to try to resolve issues. Note that in order to do so, I require you to change your password to a temporary password, that you will then change back after I am done. I don't need/want access to anyone's account for any more time than necessary. Of course, many will not want to do this, and that's 100% fine - I just want you to know it's an available option.
If the Debug Report isn't locating your dump(s) automatically, or you are manually sending a report, there are a few locations they might reside:
Note that you can always send in feedback/comments/info even without a dump. Just right-click mmoloader tray icon, Send Debug Report, and put in any info you want, attach any files (screenshots, logs, etc.) you want, and send it in.
Note that debug reports are protected on the server, so only those with the need (a couple of us) even have access to them. The 'user' mmoloader sends them up as doesn't even have access to them after sending it, fyi. Nobody else is going to get hold of your debug reports.
</your>Examples of some things you can add to your Debug Report (feedback box) or in a post here:
For connectivity and crash issues, a few things to try and eliminate as possible issues:
If you are crashing when STARTING the game, it's VERY common to be your graphics drivers/directx/EQ installation:
Here is some additional information on setting full debug dumps as well as how/what to send me via Debug Report window, if you want to provide additional information that may be helpful in resolving your issue:
If you want, you can configure your system to create full crash reports, e.g. in C:\Crash, and then when you crash it should find the proper full one (you can tell by the filename, the mini and full should have the same data/time stamps).
First, you can use one of microsoft's debugging tools, shown here: Taking Dumps with the ADPlus executable - Dan's WebDAV 101 - Site Home - MSDN Blogs
Keep in mind if you are having full dump crash creation issues, having no (or too small) of a windows swap file (paging file) can cause that issue.
Save this as EQDumps.reg and then double-click to import to your registry:
You can also, if you want, do a few of these:
1) In macroquest.ini (before you run EQ), turn on debug logging: DebugSpewToFile=1
-- That will create a DebugSpew.log in your MQ2 Logs directory (Or whatever you have the Logs directory set to in macroquest.ini)
2) Turn on EQ logging (/log)
3) Zip up your UI directory (for your custom one)
4) Hit winkey+r (or run), and run: dxdiag
--- When it asks to check if your drivers are digitally signed, click Yes. Click the Save all Information button, and save to a file (default dxdiag.txt)
On the crash when you are sending full and/or mini, click the round button at bottom for additional files, and attach:
DebugSpew.log (in mq2 logs dir)
EQ char logs (in eq logs dir)
dbg.txt (in eq logs dir, please collect before starting another eq session in that directory, or it will be cleared/overwritten with info that doesn't relate)
your UI zip
your crashing toon's .ini files from the EQ dir
your dxdiag.txt (or whatever you called it)
If you don't mind, also check the option in debug report to send past XX windows log entries (try to click that soon as the debug report window opens, so you get the ones closest before crash)
I'll try to review all that stuff and see what I can do.
If you feel uncomfortable sending me any particular item (due to toon names), that's cool, I won't take offense - but your names are safe with me.
NOTE: To see where your MQ2 files are located, right-click MMOLoader tray icon, and click System Information. In that window, you will see "MacroQuest2 Installed In". You can even hover your mouse over where it says "MacroQuest2 Installed In", click it, and it will open an explorer window in that directory.
Known Issues
This thread is for feedback concerning the latest release. Simply reply to this thread with the information requested below to report any problems or concerns relating to this release.
For a list of plugin commands please read our MacroQuest2 FAQ
This release is based on MQ2-20151118.
_______________________________________________________________
Having a problem?
If you are reporting an issue with this compile please use the Send Debug Report from MMOLoader. You can also post here with any general issue, or even to just let me know you sent a report. If you expect a personal response, in email or this thread, then provide feedback in the comment box provided in the debug report, and provide an email address. If not, then I will look at the report and make any decisions I need to based on that, but will NOT respond to you personally in email or this thread.
You're welcome to email me at htwmmo@gmail.com for any reason. Please state your mmobugs forums user name in the email so I know who to contact on forums if needed.
If you want some 1:1 support, we can try to arrange an appropriate time window to use Skype, or RDP support invitation, or TeamViewer for me to try to help with your issue. I am also willing to log into your EQ character to try to resolve issues. Note that in order to do so, I require you to change your password to a temporary password, that you will then change back after I am done. I don't need/want access to anyone's account for any more time than necessary. Of course, many will not want to do this, and that's 100% fine - I just want you to know it's an available option.
If the Debug Report isn't locating your dump(s) automatically, or you are manually sending a report, there are a few locations they might reside:
- The 'Logs' directory, under your EverQuest installation folder. For example, if EverQuest is installed in C:\Program Files\Sony\EverQuest, then the file will be C:\Program Files\Sony\EverQuest\Logs\debug.dmp.
- C:\Crash
- %LOCALAPPDATA%\CrashDumps
- %TEMP%\SCE\wws_crashreport
Note that you can always send in feedback/comments/info even without a dump. Just right-click mmoloader tray icon, Send Debug Report, and put in any info you want, attach any files (screenshots, logs, etc.) you want, and send it in.
Note that debug reports are protected on the server, so only those with the need (a couple of us) even have access to them. The 'user' mmoloader sends them up as doesn't even have access to them after sending it, fyi. Nobody else is going to get hold of your debug reports.
</your>Examples of some things you can add to your Debug Report (feedback box) or in a post here:
- Description of the problem you are having - be as detailed as possible.
- What plugin you are having an issue with (if known).(*) If applicable, attach your INI file for the problem plugin to the debug report (additional files button), and if you are worried about it, then just send a copy with any account/toon names changed or removed. NOTE: INI files for plugins can be found in your MQ2 directory). Macro INI files usually are in your Macros directory.
For connectivity and crash issues, a few things to try and eliminate as possible issues:
- Try restarting mmoloader.
- Try rebooting your PC.
- Try disabling firewall/antivirus/antispyware.
- If you use WinEQ2, Isboxer, or Innerspace, try EQ without it.
- If you use a Custom UI, try using Default.
If you are crashing when STARTING the game, it's VERY common to be your graphics drivers/directx/EQ installation:
- Try making sure you have the latest video drivers for your card. Use a cleaner utility (for AMD or Nvidia or Intel or whoever) to remove, reboot, then install latest, reboot.
- Make sure your directx is fully up to date (google dxwebsetup).
- Save your EQ install to a temp directory (rename it or whatever), and reinstall fresh, to see if you continue to experience the issue(s). It's common for some rogue setting or other file in the EQ directory to cause this kind of crash.
Here is some additional information on setting full debug dumps as well as how/what to send me via Debug Report window, if you want to provide additional information that may be helpful in resolving your issue:
If you want, you can configure your system to create full crash reports, e.g. in C:\Crash, and then when you crash it should find the proper full one (you can tell by the filename, the mini and full should have the same data/time stamps).
First, you can use one of microsoft's debugging tools, shown here: Taking Dumps with the ADPlus executable - Dan's WebDAV 101 - Site Home - MSDN Blogs
Keep in mind if you are having full dump crash creation issues, having no (or too small) of a windows swap file (paging file) can cause that issue.
Save this as EQDumps.reg and then double-click to import to your registry:
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\eqgame.exe]
"DumpCount"=dword:00000004
"DumpFlags"=dword:00000000
"DumpFolder"=hex(2):43,00,3a,00,5c,00,43,00,72,00,61,00,73,00,68,00,00,00
"DumpType"=dword:000000021) In macroquest.ini (before you run EQ), turn on debug logging: DebugSpewToFile=1
-- That will create a DebugSpew.log in your MQ2 Logs directory (Or whatever you have the Logs directory set to in macroquest.ini)
2) Turn on EQ logging (/log)
3) Zip up your UI directory (for your custom one)
4) Hit winkey+r (or run), and run: dxdiag
--- When it asks to check if your drivers are digitally signed, click Yes. Click the Save all Information button, and save to a file (default dxdiag.txt)
On the crash when you are sending full and/or mini, click the round button at bottom for additional files, and attach:
DebugSpew.log (in mq2 logs dir)
EQ char logs (in eq logs dir)
dbg.txt (in eq logs dir, please collect before starting another eq session in that directory, or it will be cleared/overwritten with info that doesn't relate)
your UI zip
your crashing toon's .ini files from the EQ dir
your dxdiag.txt (or whatever you called it)
If you don't mind, also check the option in debug report to send past XX windows log entries (try to click that soon as the debug report window opens, so you get the ones closest before crash)
I'll try to review all that stuff and see what I can do.
If you feel uncomfortable sending me any particular item (due to toon names), that's cool, I won't take offense - but your names are safe with me.
NOTE: To see where your MQ2 files are located, right-click MMOLoader tray icon, and click System Information. In that window, you will see "MacroQuest2 Installed In". You can even hover your mouse over where it says "MacroQuest2 Installed In", click it, and it will open an explorer window in that directory.
Known Issues
- MQ2PiggyZone - paths need adding for latest expansion
- MQ2GZone - /gzone not working and toons are still booted out of instance with /glock.
- EQNavigation.exe - Thuliasaur Island zone will crash when trying to build pathing mesh.
- MQ2DoCrack - One of MQ2DoCracks is causing a problem.
