I started playing on normal mode and have had the tutorial popup but no fights since. Is that normal? When can I expect the RPG part to begin?
- Thread starter Winterfire
- Start date
- Jan 15, 2018
- 102
- 74
Winterfire I recently bought a new monitor ultrawide (21:9 2560x1080) and got an issue with the menus and the game in general.
The first main menu is fine but when you go to settings and when you go to continue, the menus are scaled outside the monitor, and can't reach the options that is far up or at the bottom of the screen.
Pls, can you make the screen responsive, so they fit with the resolution correctly ?
The first main menu is fine but when you go to settings and when you go to continue, the menus are scaled outside the monitor, and can't reach the options that is far up or at the bottom of the screen.
Pls, can you make the screen responsive, so they fit with the resolution correctly ?
Hm... Weird, I will give it a try.
Black bars should show up on the left/right side, that's the expected behaviour. Nothing should really get off screen, perhaps try to reopen the game?
Also, it would be useful to know which menus are scaled outside the monitor, perhaps with a screenshot, this way I can quickly check it out while testing.
- Jan 15, 2018
- 102
- 74
Here I take some screenshots.
Main is fine (2560x1080)
Settings are scaled out the top and bottom (2560x180)
Change to 1680x1050 is stretched but I can see the buttons now
Same happens in the loading menu, buttons at the top and bottom are scaled out (2560x1080)
Thanks!
I'll check it out later today, and attempt to fix it.
Really weird, as I was sure it scaled properly... At the very least it does with some aspect ratios as I had tested in the past (and 1680 x 1050 seems to work), but I'll just check the title screen and replicate its settings/see if I have forgotten something, thanks for letting me know.
I'll let you know once I believe I have fixed the issue.
Not sure, but there will be a Ryuu route in the sequel.
All right, gave it a look and spotted the issue: I had put the incorrect setting while wrongly thinking it was equivalent, I just have to replace this setting in all UI (where it doesn't already exist, and fix other potential issues due to this change) and the issue will be fixed.
Everything should work fine from R25 on, thank you once again for letting me know about the issue!
- Mar 21, 2022
- 707
- 715
the banquet of tradegy
i asked about the xenos arc and that´s what Winterfire said:
Xenos arc and anything in volume 8/S3 on will happen in the sequel whose save you can import, if you want to keep the choices/equipment/stats from this game.
As of R24, the game reached its last chapter, and now I am making the epilogue and refining the game as much as possible by solving all the issues in the todo list.
so will be in a while
- Mar 21, 2022
- 707
- 715
Yes, but Volume 8 is also covered in this release, since it is pretty much a collection of side stories.
Those relative to the heroines in the game and the MC will be covered in a form or another.
The sequel will begin from Volume 9.
- Jan 15, 2018
- 102
- 74
Hey, it seems that the game has been freezing whenever i try to load into the dungeon for the 2nd time (after the first time you're allowed to use the hub). Is this a known issue, or is there a workaround?
This issue has been fixed on R24: Fixed: Load game from Dungeon makes the game crash or not unload the Dungeon.
However, if that is the issue, the game should still be playable (hence why the bug flew under my radar for so long) as long as you do not load a game from within the Dungeon.
-edit-
If it is another issue unrelated to this, simply attach the player.log and it should show the reason for the crash.
The most recent file on F95 is R22, but the problem isn't from loading in the dungeon from the save screen, its from trying to enter the dungeon from the hub screen.
Apparently the player.log file is too large to attach here, but I took a look through it and the last few lines look like this:
d3d11: failed to create buffer (target 0x1 mode 1 size 186720) [0x887A0005]
d3d11: failed to create buffer (target 0x2 mode 1 size 23340) [0x887A0005]
d3d11: failed to create buffer (target 0x1 mode 1 size 212256) [0x887A0005]
d3d11: failed to create buffer (target 0x2 mode 1 size 26532) [0x887A0005]
d3d11: failed to create staging 2D texture w=128 h=2 d3dfmt=10 [887a0005]
d3d11: failed to create staging 2D texture w=128 h=2 d3dfmt=10 [887a0005]
d3d11: failed to create staging 2D texture w=128 h=2 d3dfmt=10 [887a0005]
d3d11: failed to create staging 2D texture w=128 h=2 d3dfmt=10 [887a0005]
d3d11: failed to create staging 2D texture w=128 h=2 d3dfmt=10 [887a0005]
The last 5 lines just keep repeating.
You can post the full log somewhere and give me the link, unless your GPU is already under stress or it needs its drivers updated, my best guess is that it is running out of memory.
What are your hardware specs? The log (on the top) also tells whether your game is running on your actual GPU, or an integrated GPU by mistake, if you are on a laptop.
What floor are you trying to go in? And have you tried another floor and see if the error happens anyway? Some floors are slightly more demanding, such as floor 8+ which are completely covered in grass, and Floor 10+ which are covered in grass and fog.
I've cut out a bunch of the repeating lines at the bottom. I'm playing this in a VM which might be the issue.
Oh wow, 128mb vram. That's the issue.
This confirms it is running out of memory, even on the lowest settings it is going to use way more than that.
I think only Story Mode would run fine as it does not consume too much vram.
If you can allocate more vram to your VM, it might fix your issue.
In the Dungeon, the textures alone are about 16mb each, and a material often has a few of those.
I think the only level you could run on that is the tutorial, even the first floor has many materials which are going to either get very close to 128, or even beyond that.
I think the only level you could run on that is the tutorial, even the first floor has many materials which are going to either get very close to 128, or even beyond that.
Apparently the normal "memory" option isn't what I needed...
Fixed and working now, thanks for the help!
