|
|
Post by Nemjen on Feb 21, 2016 7:50:01 GMT -8
May not be a bug so much as a limitation, but using the 'store' or 'upgrade' to purchase and then using the scroll wheel to go backwards in dialogue will revert any purchases you have made.
There also seems to be some form of interaction with 'battle stations' and 'proceed' and reloading saves (all saves tested are 12.4a) and using the history log. So for example say I reload a previous save then I am able to use the scroll wheel to access the log no problem, however if after getting 'battle stations' you press proceed and then attempt to re load a save into a dialogue section you will be unable to use the scroll wheel to access the log until you complete another battle scenario either one from a previous save or the one that you entered with 'proceed'. (Hope that makes sense).
|
|
|
|
Post by Marx-93 on Feb 21, 2016 12:02:59 GMT -8
Have to confirm this, though I'm a tad unsure on the second part. In my case I was often unable to go back after I spent a suitable amount of time and resources in either the store or the upgrade, which, while avoided the problem of unknowingly undoing your upgrades, it kinda destroyed the log option which is kinda a must for Visual Novels.
In any case, I think it's kinda important, specially with how much of "game feel" has shifted to a more "Visual-novel like" experience.
|
|
|
|
Post by Nemjen on Feb 21, 2016 12:20:40 GMT -8
Have to confirm this, though I'm a tad unsure on the second part. Yeah apologies I was aware I was not really describing it well enough, an interaction I have noticed in a few instances now is that if you play the game as normal and get up to a 'battle stations' screen just before a scenario the scroll wheel log works fine, however this changes after you press 'proceed' - if during deployment or during the mission itself you reload to an earlier save that is in before or after a scenario (the dialogue sections) you will be unable to use the log using the scroll wheel. It seems to function as normal if you jump between saves that are during dialogue sections of the game (non scenario) however once you get past a proceed button the only way to get the feature working again is to clear a scenario. Step One: You play the first scenario and beat it, proceeding to the dialogue section. Step Two: During this section you go through a couple of scenes and create a save point, making note to test the scroll wheel. Step Three *Optional*: Load another save that is dialogue based and test the scroll wheel again - it should still work. Step Four: Now go back to your original save in step two and continue until you get to the 'battle stations' screen, press 'proceed'. Step Five: Either during deployment or at some point during the second mission scenario save and then reload the previous save you made for the step two - try the scroll wheel again. The log will not trigger and you will be unable to display previous content. Step Six: Reload the save from step five and complete it, in a similar sense to step two go through a couple of scenes and create a save. Testing the scroll wheel you will notice you are able to view the log again. Step Seven: Go back to the original save outlined in step two and try the scroll wheel again, it is working again. Does that help in anyway? |
|
|
|
Post by vaendryl on Feb 21, 2016 23:16:22 GMT -8
This sounds like a bug in renpy itself  I don't think I can fix this but I'll try. obviously, you shouldn't be able to roll back during battle, and even in MoA using the upgrades screen or the store blocks rollback from that point. it's just a technical limitation to renpy, as the whole rollback system basically uses a system similar to constant save states. |
|
|
|
Post by Nemjen on Feb 22, 2016 0:05:24 GMT -8
It did feel like a limitation rather than a bug, anything you can do would be appreciated thanks.  |
|
|
|
Post by Marx-93 on Feb 22, 2016 14:04:40 GMT -8
To be honest, while Renpy's rollback feature is very nice, at this point I think a proper log with a "repeat voice" option would definitely be the best option (at least for the unavoidable 13.1 or 13.2).
|
|
|
|
Post by Nemjen on Feb 22, 2016 16:05:43 GMT -8
With just over a week to go though, is this sort of feature realistic? I get the feeling that it is a bit too late (at least for now) in the project life cycle to re work a system feature as this would trigger a need for additional development, testing and optimising which are already quite tight. Not saying it is a feature that I would not like see, heck I would much prefer a traditional log that is separate from the how Renpy uses save states but at this time it is technically an enhancement and the game should really be starting to enter its final stable state. Saying that I might be proved wrong, Samu-Kun may actually feel as though there is time to look into this before the launch but that would be down to his discretion. Post launch I am sure I read somewhere that the LiS team is considering future enhancement patches (and no not the neko DLC  ) which technically this could be something that is bundled into, I am sure those of us lurking around here would have no problem helping with the testing before public release if this was something they decide to do. |
|
|
|
Post by Marx-93 on Feb 23, 2016 1:08:51 GMT -8
With just over a week to go though, is this sort of feature realistic? I get the feeling that it is a bit too late (at least for now) in the project life cycle to re work a system feature as this would trigger a need for additional development, testing and optimising which are already quite tight. Not saying it is a feature that I would not like see, heck I would much prefer a traditional log that is separate from the how Renpy uses save states but at this time it is technically an enhancement and the game should really be starting to enter its final stable state. Saying that I might be proved wrong, Samu-Kun may actually feel as though there is time to look into this before the launch but that would be down to his discretion. Post launch I am sure I read somewhere that the LiS team is considering future enhancement patches (and no not the neko DLC ) which technically this could be something that is bundled into, I am sure those of us lurking around here would have no problem helping with the testing before public release if this was something they decide to do. Did you read the "(at least for the unavoidable 13.1 or 13.2)" part? 7.2 needed more than 6 months to reach us. I know it won't be ready for the 4th (though I think that this release date is overeager, specially with very big amount of issues found in in Beta 12). |
|
) which technically this could be something that is bundled into, I am sure those of us lurking around here would have no problem helping with the testing before public release if this was something they decide to do. 
Hot singles in your local solar system! 
