- Mar 15, 2012
- Reaction score
I'm trying to use your ItemGenerator tool, but it's taking too long to load the resources. My questions are; Is it my computer? I have a Windows 10, 64 bit, 4 GB RAM, VAIO. Maybe my computer is too slow to run the .exe. If not, what am I doing wrong? I already changed the compatibility to Windows 7, the program started but the resources are taking to long to load, about 15 min on Background Circles, is that normal?
Please instruct me
I'm afraid I can't help you there. The resource loading process is a part of the software that's needed.
Yanfly did you miss my post?
I did now. Please follow all of these instructions when doing a bug report:
ALL bug reports MUST follow these guidelines and use this template:
Plugin Name: (What is the name of the plugin?)
Bug Explanation: (What is the bug in your own words? Keep this detailed. "It isn't working right" is not a valid bug report.)
Error Report: (If you received an error message, press F8 when the message is received to open up the debug console, then copy/paste the entire error log and paste it here).
Exact Steps on How to Replicate Bug: (Write out IN DETAIL, a step-by-step guide on how to replicate the bug.)
Sample Project (REQUIRED): A sample project MUST be attached to the bug report. All steps MUST be followed. If a single step is ignored, the bug report is invalid and I will move on to the next bug report.
1. Download all the newest updates of the plugin.2. Create a new project. Do NOT just copy over your game project folders. This should be just a stock, empty, new RPG Maker MV project. If I do not see an empty project with Harold, Therese, Marsha, and Lucius, I will not look any further.3. If the project's file size is above 200 MB, remove unnecessary audio and image files until you reach that size. Usehttp://forums.rpgmakerweb.com/index.php?/topic/47985-mvstripper-remove-unused-assets-from-your-mv-project/ if you need some help doing so.4. Install -only- the affected plugins. If you're using non-YEP plugins, do NOT include them.5. Do -NOT- rename the plugins' filenames. They cease to work if you do so.6. Make sure they're in the EXACT order listed on http://yanfly.moe/yep/. The ordering of plugins is important.7. Recreate the error in the sample project. MAKE SURE you are using notetags in the right place and haven't misspelled anything.8. Archive the project with WinZip or WinRAR. Do not archive it multiple times. It does not compress it further.9. Do -NOT- deploy the project through File > Deployment. Upload the project online to a website like MediaFire.com or Mega.co.nz or Dropbox. Please do not use a website that involves timers like 4shared, RapidShare, etc. If I am time-gated from downloading the project, I will ask you to reupload it to somewhere else.10. Post the link here and I'll take a look at it.
Sorry for my "english" I am not native speaker
Plugin Name: YEP_X_TickBasedRegen
Bug Explanation: In CTB system, this plugin collide with few more plugins modifying states. For example with YEP_AutoPassiveStates or YEP_RowFormation states (added as plugin parameters for each row).
Bug happens IF you ADD Actor during battle (for example as Summon Skill or as add in troops table - Battle Event)
at Game_Actor.Game_Battler.updateTick (/E:/XEEN/BUGPROJECT/js/plugins/YEP_BattleEngineCore.js:3625)
at Game_Actor.Game_Battler.updateTick (/E:/XEEN/BUGPROJECT/js/plugins/YEP_X_BattleSysCTB.js:1671)
at Game_Party.Game_Unit.updateTick (/E:/XEEN/BUGPROJECT/js/plugins/YEP_BattleEngineCore.js:3942)
at Function.BattleManager.updateBattlerCTB (/E:/XEEN/BUGPROJECT/js/plugins/YEP_X_BattleSysCTB.js:976)
at Function.BattleManager.updateCTBPhase (/E:/XEEN/BUGPROJECT/js/plugins/YEP_X_BattleSysCTB.js:896)
at Function.BattleManager.update (/E:/XEEN/BUGPROJECT/js/plugins/YEP_X_BattleSysCTB.js:858)
at Scene_Battle.updateBattleProcess (rpg_scenes.js:2051)
at Scene_Battle.update (rpg_scenes.js:2043)
at Scene_Battle.update (/E:/XEEN/BUGPROJECT/js/plugins/YEP_BattleEngineCore.js:3963)
Exact Steps on How to Replicate Bug: Plugins required: Yep_CoreEngine, Yep_BattleEngineCore, Yep_X_BattleSysCTB, Yep_BuffsStatesCore, YepY_Tick_Based_Regen, YepAutoPassiveStates.
Create class and actor with AutoPassive State <Passive State: 11>
Create State ID 11 - it could do nothing or anything, does not matter.
Create skill or Battle event with Change Party Member - Add Actor (one with passive skill). You will receive ERROR "Cannot Read Property "11" of Undefined" - where 11 is ID number of passive state of summoned actor.
Sample Project (REQUIRED): BugProject uploaded (I hope just JS and Data folder is enough without IMG/Audio)
View attachment 38590
Next time, do not simply just delete the non-JS and Data folders. It took a good 10 minutes for me to set all of this up because of the lack of preparation and me constantly adding sufficient resources to get everything working. That pretty much summed up the free time I had in my break and I won't be able to fix this until much later.
Plugin Name: YEP_X_ActSeqPack2.js
Bug Explanation: I started a battle and I get this... That's all the explanation I can give. I know this didn't happen until I updated the plugins in the most recent update [5-23-2016].. It happened in my project and I tried a new project with just the plugins listed below [Project file provided] and it happened there as well. I got the plugins from your dropbox link just a couple of hours ago so I know their all up to date.
Exact Steps on How to Replicate Bug: Plugins required: Yep_CoreEngine, Yep_BattleEngineCore, Yep_X_BattleSysCTB, Yep_X_ActSeqPack1-3
Just start a battle... that's it
Sample Project (REQUIRED):
Link is incomplete.
Plugin Name: YEP_TargetCore, YEP_BattleSelectCursor and YEP_BattleEngineCore
Bug Explanation: Actions who target each battler don't select allies, only foes.
Error Report: None.
Exact Steps on How to Replicate Bug: Give a <Target: Everybody> notetag to any skill or item.
Try to use it, you will see crystals only above the enemies, but none above your party.
Sample Project : http://www.mediafire.com/download/h4ib54etd71pzuv/Debug.zip
Thanks for the catch. I'll get this fixed!