eromancer
patreon
April Progress Update!
🕑 Added 2017-04-01 20:42:24 +0000 UTCHey everyone!
As usual, there’s a whole lot to report on for this month! We’ve been making solid progress, and I want to thank you for sticking it out while we go through this dry spell of playable content. Alas, production for v0.06 is still sidelined for a little bit longer while I finish up work on the game’s story. While it may not be the news you were hoping for, it’s not bad news! I’ll get to that more in a second. While I’ve actively been the wrench in the machine holding up v0.06 with my story shenanigans, AltairPL has been making *incredible* progress on the new engine. So much so that I’ve gotten ahead of myself (much to APL’s chagrin) and started drafting mock-ups to understand what changes will be required by the game’s art. Here’s a little comparison mock-up of what you can expect the battle scene to look like in glorious HD! Of course, APL would kill me if I didn’t put a little disclaimer saying this is still completely tentative, will require a lot of work, and is still quite a way off, so there it is 😃. Anyways, APL has a new engine tech demo that we really need your feedback on! The more feedback we get from you at this early stage, the fewer bugs we will have when we make the engine transition. This tech demo includes all his progress since the one we showed off to the Inner Circle crowd earlier this month, so please see below to check it out!
Story Progress
I’ll admit when I started the project I wasn’t really planning for the story to be such a priority. It’s actually turning out to be one of the things I’m most proud of though! It’s come a looooong way since my original rough draft last year, and I think it has the potential to be as epic as the games that inspired the project. I’m also pretty certain you won’t be disappointed by the amount and variety of H content… nor in the fact that you will now get to play five different characters throughout the game! Sitting on the story details is burning me up, but what I can share with you (without really spoiling anything) is something I showed the Inner Circle crowd earlier this month. A couple weeks back I finished the core elements, and after doing so I divided the game into five chapters with a number of subsections. The above image shows the tentative organization and names of these sections. This idea was inspired by how the RPG classic Chrono Trigger's story was organized and presented to the player, and just like that game I plan to somehow make these visible within the game as you progress through them.
For the past couple of weeks I’ve been working on what I’m calling the “final pass”, in which I started at the beginning and have been filling in gaps and revising anything that needs it. Admittedly, that name is misleading since I’ve already resigned to the fact that later on there will need to be probably another month down the road where at the very least more scriptwriting is done. It’s been a huge task, and while things are going great creatively the hold-up is due to the sheer amount of work. It’s over a hundred pages already, and by the end of it I expect the script alone to top 100, not including the H scene dialog.
The good news is that I’m quite confident there won’t need to be any major rewrites at this point, and as such I’m nearing the point where I can say enough is enough for now and jump back onto v0.06 production!
APL’s Engine Progress
APL here! Before I start my progress report, I feel like I need to clarify few things since it's getting a bit confusing (apologies to the Inner Circle crowd, who has already read through this… see the bottom of this section though for the latest progress update)!
For the most part, the engine progress mentioned in last monthly update was referring to interfacing SDL/GPU directly from the game ruby scripts. For the sake of clarity I'll refer to that as "RM_SDL" from now on. Then there was this line from the last monthly update:
"Currently APL is investigating ways to simplify the interfacing between Ruby and C, which has been causing him a lot of uh, mental trauma."
This line from the last monthly update is referring to an entirely new approach which is covered in more details below. The confusing part is that the last monthly progress update mixes information about both approaches, and even though all of that information is still valid, I want to make a clear and definite distinction of what was and what is.
RM_SDL showed a lot of promise, but to make it work I had to, and would constantly have to, either make some changes to SDL/GPU library or create and maintain a proxy library of my own. Another problem was that no matter what I did, RM was throwing wrenches into my gears. Those and other problems (e.g. uncontrollable memory leaks and other "fun" stuff) were getting old pretty fast, and it was really getting on my nerves... so I made a kind of extreme decision to make a similar game engine of my own. This is the new approach vaguely mentioned near the end of the monthly progress update.
Here’s an update on that!
The codename for new engine is URGE (Universal Ruby Game Engine). I had a few similar names in mind, but URGE kinda fits the H nature of the first (and hopefully not last) game based on it - MATM.
First thing I had to do was to learn a boatload about the C language, application/library development in general, compilation, linking, Ruby C API, and other boring and convoluted crap. I'll skip the gory details... suffice to say, this was the reason for aforementioned mental trauma.
I then had to actually embed the Ruby interpreter into the application. This will require a lot more work down the road, but the most crucial stuff like executing ruby scripts from files/memory, exception handling/reporting, etc. are already up and running.
With basic stuff working, I moved to the next stage, which is the current work in progress: actually making URGE compatible with RPG Maker and in turn be able to use all the work we did for MATM from the start.
This image is an excerpt from the RPG Maker help file. All of the stuff visible here has to be implemented (with few exceptions) to make both engines compatible. I’ll save you the pages of technical details about what this stuff actually does, but something you’ll surely be interested in is how far along I am with it! You can find the most up to date progress chart for RPG Maker compatibility here. Things implemented into the new URGE engine since the last Inner Circle update (last week) are indicated with the (NEW) tag.
AltairPL’s New Engine Tech Demo (Feedback Needed!)
APL here again! You can find the new engine’s tech demo files here (click download in the top right of the screen). Before you start the tech demo, please, read everything in this section!
This engine tech demo is an updated version of the one shown to the Inner Circle crowd a couple weeks back. It’s not supposed to be flashy, it’s just a simple program designed to test the basic functionality of the engine. It may not look like much, but it actually serves two very important purposes:
- Show all of you how the work on the new engine is progressing,
- Allow me to gather some early feedback on how it looks and works, including issues that may occur on some configurations.
Before I go into details I need to address one very important thing. URGE is using a physical keyboard layout instead of the logical one (like RPG Maker does). This means that all keys listed below and in the keys.txt file are referring to physical position of keys on QWERTY keyboard. If you use a different keyboard layout, like AZERTY, QWERTZ, etc., you can use following image as a reference: https://en.wikipedia.org/wiki/File:Qwerty.svg . The problem is that everyone on the MATM development team uses QWERTY keyboard, so I'm not even sure if this paragraph is correct - if not, please let us know! Also let us know if you think that this approach is not the best idea. It's not set in stone and we’re open to suggestions. Also, please remember that this engine is still a very early prototype coded in a language I barely know, so some things may be sub-optimal. I'm doing my best, but most likely I couldn't avoid making some stupid mistakes, so please be patient with me and don't be angry if something doesn't work as it should or doesn't work at all.
As I've said, one of the reasons for this tech demo is to gather early feedback. There's quite a lot of info we could use from all of you and every report is much appreciated.
- First thing we need is the RendererInfo.txt file, which is created during the application start. At least basic info should be included in case of a crash, so if it exists, please send it to us.
- In the tech demo folder, you can find a reference.png image, which represents how the tech demo window contents should look like after the start - let us know if something is off and include a screenshot if you can.
- Another important thing is performance. This point is especially important for computers with low specs or just old ones. We could especially use some test information from those of you with computers that have integrated graphics! By default, the engine frame rate is capped to 60 FPS. You can toggle title bar FPS counter using F2 key and decrease/increase the limit using F7 and F8 keys respectively. Unfortunately, my implementation of the FPS counter is not entirely accurate with very high frame rate values, and displayed value may fluctuate a lot. If the value on the left is hovering below the value on the right, this is the value we need.
- Please let us know if full screen mode works! F3 will toggle full screen window mode on / off, whereas F4 will toggle the actual full screen mode on / off. We’re especially curious if the F4 mode works for everyone, since I’m not certain it’s working exactly as it should.
- There are a lot of places where error checks should be added, but for various reasons aren't. Please let us know if it crashes at any point, or if you receive an error popup!
- It's not mandatory, but providing some information about the computer on which above data was gathered would help us a lot in compiling basic system requirements - CPU, RAM, GPU, VRAM, etc.
I've spent a lot of time on window functionality. There's probably a lot more to do, but here's the rundown of currently implemented things:
- You can freely resize and maximize/restore the window. Contents will be scaled accordingly while retaining aspect ratio. In some cases /configurations this may result in blurry image – this is in part due to low resolution assets from the original game being upscaled (we plan on adding high resolution artwork once the engine goes live).
- At runtime, if usable display area is smaller than the tech demo window, the window will be scaled down accordingly.
- Two full screen modes currently exist (see the above list of feedback we could use from you for details)
- Do note that at this time there's no way to restore the window to its initial size, but I'd very much like to implement something somewhere along the line.
Now for the other tech demo functionality:
- The Corruptor head at the upper edge of the window should swing like a pendulum.
- Arrow keys control movement of the grid located in the middle of the window.
- A, S, and D keys randomize Neon's Color, Tone, and Opacity respectively and Q key resets those values.
- Z, X, C, and W keys do the same for Malise.
Thank you in advance for taking the time to test the tech demo and for all the feedback you provide!
TK’s Environment Art Progress
TK’s kind of been all over the place this month 😃.
As mentioned in the last monthly update, TK had shifted focus to working on environment assets for future areas of the game. Toward the end of February and into the early part of March however, he had actually taken a break from this to attempt an experiment that would have helped me a lot with armor damage artwork. The goal was to come up with a system that would enable us to create Malise’s armor damage artwork completely in 3D, meaning much less post work in terms of painting. Unfortunately, it didn’t pan out, and we came to the conclusion we’d need to create a much more in depth system to avoid deformation/stretching when her hips and thighs are animated. Since this isn’t a priority at the moment I had him jump back onto environment work.
His next area of focus was on a sewer area that will make an appearance a few updates out. This area was originally intended to be much earlier in the game, so there was some design work already done for him to go off of. One of his major goals however was to figure out a solution for creating realistic water graphics that we can implement for the new map upgrades we’ve been using since V0.05. The possibility from the new engine of vastly improved load times and ability to use GPU memory opens some doors in this area, so creating larger scale, non-tiling animations for environment backgrounds is now on the table. He successfully managed a proof of concept, and while it’s not jaw-dropping yet, the point is that we now have a system worked out for when we need it.
For week 3 he changed things up again:
TK here! This week I've been re-examining how I render scenes and a little bit of asset management. I spent a couple of days with Unreal Engine 4 with the idea of rendering out final backdrops there. There's a lot of great stuff going on under the hood, but I think in comparison with my current workflow, the cons outweigh the pros as a whole. But at least my curiosity is satiated, I'll probably try to set some time to goof off with UE4 more in the future. I still have an asset crisis that's growing every day! I don't have the luxury of being VerySmart(tm) or having a person working on pipeline tech, so I'm still stuck with scenes bloated with too much to manage (but it works for now).
From there, I went back to trying to solve some issues I've been having with Mental Ray lights and materials, and managed to get some small boosts in my render times (maybe). ...and I finally wrapped my head around getting mesh lights to work properly without totally destroying everything around them!! Neon tubes, signage or shaped lights are examples of where I'll be using this.
Last but not least, here’s a compilation of some of TK’s conversions and custom models from this month!
Comments
AltairPL
No problem... happens to the best of us ^^. That's a load off my mind, so thank you for testing it again.
Panthear
Ups.. my bad. Yes it was the Graphic driver. I am a little ashamed that I forgot to update it. After update everything runs fine: Available renderers: * OpenGL 1 BASE (1.1) * OpenGL 1 (1.1) * OpenGL 2 (2.0) * OpenGL 3 (3.0) * OpenGL 4 (4.0) Renderer init order: 1) OpenGL 4 (4.0) 2) OpenGL 3 (3.0) 3) OpenGL 2 (2.0) 4) OpenGL 1 (1.1) Using renderer: OpenGL 4 (4.0) Shader versions supported: 110 to 400 Enabled Features: 0x00000FDF: - GPU_FEATURE_NON_POWER_OF_TWO - GPU_FEATURE_RENDER_TARGETS - GPU_FEATURE_BLEND_EQUATIONS - GPU_FEATURE_BLEND_FUNC_SEPARATE - GPU_FEATURE_BLEND_EQUATIONS_SEPARATE - GPU_FEATURE_GL_BGRA - GPU_FEATURE_GL_ABGR - GPU_FEATURE_VERTEX_SHADER - GPU_FEATURE_FRAGMENT_SHADER - GPU_FEATURE_PIXEL_SHADER - GPU_FEATURE_GEOMETRY_SHADER - GPU_FEATURE_WRAP_REPEAT_MIRRORED
AltairPL
I finally had some time to do some research on the Intel GPU issue, and I'm pretty sure that used GPU drivers are to blame. Not only older driver versions had limited Shader Language support (similar to 1.10-1.30 you reported), but also with newer drivers OpenGL 4.0 should be supported as well. I would appreciate if you could update your Intel GPU drivers and try the Engine Tech Demo again.
That's how I've been playing MATM this whole time so I figured I'd give it a shot :)
AltairPL
I wasn't expecting someone will try running it under Wine, so thanks for this :D
Linux 64-bit using Wine 1.9.20, 16GB RAM, AMD Phenom II X4 960T, GTX 970 Available renderers: * OpenGL 1 BASE (1.1) * OpenGL 1 (1.1) * OpenGL 2 (2.0) * OpenGL 3 (3.0) * OpenGL 4 (4.0) Renderer init order: 1) OpenGL 4 (4.0) 2) OpenGL 3 (3.0) 3) OpenGL 2 (2.0) 4) OpenGL 1 (1.1) Using renderer: OpenGL 4 (4.0) Shader versions supported: 110 to 400 Enabled Features: 0x00000FDF: - GPU_FEATURE_NON_POWER_OF_TWO - GPU_FEATURE_RENDER_TARGETS - GPU_FEATURE_BLEND_EQUATIONS - GPU_FEATURE_BLEND_FUNC_SEPARATE - GPU_FEATURE_BLEND_EQUATIONS_SEPARATE - GPU_FEATURE_GL_BGRA - GPU_FEATURE_GL_ABGR - GPU_FEATURE_VERTEX_SHADER - GPU_FEATURE_FRAGMENT_SHADER - GPU_FEATURE_PIXEL_SHADER - GPU_FEATURE_GEOMETRY_SHADER - GPU_FEATURE_WRAP_REPEAT_MIRRORED It all ran fine for me, with no graphical issues or lag.
AltairPL
Thanks. I already know the reason for the XP issue, since I've read about it some time ago, but not counting one convoluted workaround I have nothing solid on it yet. No idea yet what's the cause and fix for Intel HD issue. I'm kinda busy with another problem I have, but I'll try to do some research and do something with those two - thanks again for reporting them.
Panthear
O.k. 32-bit Windows XP No go: "The procedure entry point _gmtime64_s could not be located in the dynamic link library msvcrt.dll". I assume that is expected, so no measurements from older envs.... ;) PS: Images about the "X" sent.
AltairPL
Wow, that's just awesome, thank you very much :D. "No problems (except that the ESC key on QWERTZ did the same as the X Key)" That's normal. Hardware keyboard layout is used instead of a software one, but RPG Maker mappings are already implemented, and by default those two keys are assigned to the same "virtual button". "Interestingliy the Color/Tone/Opacity for the figures was not over the figure, but more like an "X". So one like 4 different colors of Red" Would you be so kind as to take a screenshot and upload it somewhere or send it to eromancergames@gmail.com ? "PS: I could also try it on an even older Laptop with WinXP, if interested...." You'd be my personal hero, at least for a while, if you could ^^.
Panthear
Win7 64bit, 12GB RAM, i7 930 (2,8 gHZ), GTX 480 => Max FPS on 1920x1080: approx 2500 Available renderers: * OpenGL 1 BASE (1.1) * OpenGL 1 (1.1) * OpenGL 2 (2.0) * OpenGL 3 (3.0) * OpenGL 4 (4.0) Renderer init order: 1) OpenGL 4 (4.0) 2) OpenGL 3 (3.0) 3) OpenGL 2 (2.0) 4) OpenGL 1 (1.1) Using renderer: OpenGL 4 (4.0) Shader versions supported: 110 to 400 Enabled Features: 0x00000FDF: - GPU_FEATURE_NON_POWER_OF_TWO - GPU_FEATURE_RENDER_TARGETS - GPU_FEATURE_BLEND_EQUATIONS - GPU_FEATURE_BLEND_FUNC_SEPARATE - GPU_FEATURE_BLEND_EQUATIONS_SEPARATE - GPU_FEATURE_GL_BGRA - GPU_FEATURE_GL_ABGR - GPU_FEATURE_VERTEX_SHADER - GPU_FEATURE_FRAGMENT_SHADER - GPU_FEATURE_PIXEL_SHADER - GPU_FEATURE_GEOMETRY_SHADER - GPU_FEATURE_WRAP_REPEAT_MIRRORED No problems (except that the ESC key on QWERTZ did the same as the X Key) Win 7 64bit, i5-3320M, (2,6 gHZ), Inttel HD Graphics 4000 => Max FPS on 1920x1080: approx 258 Available renderers: * OpenGL 1 BASE (1.1) * OpenGL 1 (1.1) * OpenGL 2 (2.0) * OpenGL 3 (3.0) * OpenGL 4 (4.0) Renderer init order: 1) OpenGL 4 (4.0) 2) OpenGL 3 (3.0) 3) OpenGL 2 (2.0) 4) OpenGL 1 (1.1) Using renderer: OpenGL 3 (3.0) Shader versions supported: 110 to 130 Enabled Features: 0x00000FDF: - GPU_FEATURE_NON_POWER_OF_TWO - GPU_FEATURE_RENDER_TARGETS - GPU_FEATURE_BLEND_EQUATIONS - GPU_FEATURE_BLEND_FUNC_SEPARATE - GPU_FEATURE_BLEND_EQUATIONS_SEPARATE - GPU_FEATURE_GL_BGRA - GPU_FEATURE_GL_ABGR - GPU_FEATURE_VERTEX_SHADER - GPU_FEATURE_FRAGMENT_SHADER - GPU_FEATURE_PIXEL_SHADER - GPU_FEATURE_GEOMETRY_SHADER - GPU_FEATURE_WRAP_REPEAT_MIRRORED Interestingliy the Color/Tone/Opacity for the figures was not over the figure, but more like an "X". So one like 4 different colors of Red PS: I could also try it on an even older Laptop with WinXP, if interested....
Panthear
Hi,
AltairPL
Sorry for the spam, but I think I figured out what the problem might be - make sure that tech demo is in path with Latin characters only... that means no diacritic signs, kanji and similar characters, etc. I'm working to fix this, but most likely we won't be reuploading the tech demo, so if you want to test it, please move it to folder like "C:\MATM URGE Tech Demo". Once again sorry for the spam, inconvenience and thanks for reporting it.
AltairPL
Erm, I just had the same exception message, but I was doing some crazy shit at the time. Anyway, I did some more testing after that and I can add one more thing for you to try: 5. If you're using shortcut to start the tech demo, make sure that "Start in:" field points to the tech demo folder or try running the tech demo executable directly (without a shortcut).
I doubt it unfortunately. The story has consumed nearly all of my time since February.
AltairPL
You're the first person to report this. No idea why it doesn't work, but I would really like to know. File mentioned in the error message is included in the archive and I see no reason why opening it could fail. Would appreciate if you could try the things below and tell me if something helped: 1. Check if all files from the archive are present in the tech demo folder, especially said "tests.rb" file. You can try extracting all files from the archive again, either way. 2. See if there's "RendererInfo.txt" file in the tech demo folder (created by the tech demo). If not, folder in which tech demo resides may have restricted read/write permissions. Try moving/extracting tech demo to a different folder - some system folders like "Program Files" are a big no-no. 3. Even if file from point 2 is in the tech demo folder, try moving/extracting tech demo folder elsewhere anyway. 4. It shouldn't be causing any troubles, but you can try temporarily disabling anti-virus protection for the duration of extracting tech demo archive and running the tech demo itself. I'm out of ideas, so I really hope one of the above will fix your problem.
Purple Witch
Hello! I had this exception (and I couldn't load other commens and see if I was the only one. <a href="http://imgur.com/a/utvRl" rel="nofollow noopener" target="_blank">http://imgur.com/a/utvRl</a>
AltairPL
Thanks for the report. There's just too many settings to list them all, but you can change the internal resolution with Graphics.resize_screen([width], {height}) - it's recommended to put it at the very beginning of the file, since image positions are calculated from it. Also do note that this will not change size of the window itself (you'll have to resize it by hand) and that the images will retain their sizes, so there will be a lot of black/blank spaces (especially near background image). Have fun ^^.
Victor Alvares
Hi, here is my pastebin - <a href="https://pastebin.com/pCM0i8am" rel="nofollow noopener" target="_blank">https://pastebin.com/pCM0i8am</a> Could you please give a short guide on how to play with the values in tests.rb file. I am interested in resizing the screen and checking with the native aspect ratio of the screen.
Do you think V0.06 will be realeased by the end of this month?
AltairPL
Thanks. And yeah, I should probably set some kind of minimum size. P.S. AMD FTW :D
AltairPL
Thank you for clarification on both points, much appreciated.
dudman
Right, I did that and the F4 seems that it follows Screen resolution settings, also for the AZERTY side note, well, it reacts like if the keyboard was a querty one(Just a little disorienting at first but with the little image you posted, it was easily to overcome, so I suggest no changes on that part)
Available renderers: * OpenGL 1 BASE (1.1) * OpenGL 1 (1.1) * OpenGL 2 (2.0) * OpenGL 3 (3.0) * OpenGL 4 (4.0) Renderer init order: 1) OpenGL 4 (4.0) 2) OpenGL 3 (3.0) 3) OpenGL 2 (2.0) 4) OpenGL 1 (1.1) Using renderer: OpenGL 4 (4.0) Shader versions supported: 110 to 450 Enabled Features: 0x00000FDF: - GPU_FEATURE_NON_POWER_OF_TWO - GPU_FEATURE_RENDER_TARGETS - GPU_FEATURE_BLEND_EQUATIONS - GPU_FEATURE_BLEND_FUNC_SEPARATE - GPU_FEATURE_BLEND_EQUATIONS_SEPARATE - GPU_FEATURE_GL_BGRA - GPU_FEATURE_GL_ABGR - GPU_FEATURE_VERTEX_SHADER - GPU_FEATURE_FRAGMENT_SHADER - GPU_FEATURE_PIXEL_SHADER - GPU_FEATURE_GEOMETRY_SHADER - GPU_FEATURE_WRAP_REPEAT_MIRRORED OS: Windows 7 MB Chipset: AMD 990FX GPU: Radeon R9 290 4GB GDDR5 CPU: AMD FX 8320E RAM: 16GB MAX FPS ~3200/3840 Both Full screen buttons work as expected. Window resizing works without issue. Just a note that there is a minimum window width but no minimum window height. All buttons presses return expected actions on QWERTY
AltairPL
Hehe, yeah, it does that ^^. But, in this case, those ish numbers are what's I was after. Thanks :D
Yuni Hermit
I had not tested that. It was 4 am and I forgot. xD But I tested it just now. No, when I press F8 a bunch to raise the frame rate, it spikes rapidly. At my max setting (7 thousand something), it bips between 630-ish to 650-ish, numbers flashing too fast to read. On another note, this makes the corruptor head split up into multiple visible after-images in a hilarious manner!
AltairPL
Laptop name is enough - I'll look it up if I need the specs, so don't worry. Just to clarify, does FPS stays at 60 when you press F8 to raise the FPS limit, like "60/120" or haven't you used F7/F8 keys?
Yuni Hermit
Available renderers: * OpenGL 1 BASE (1.1) * OpenGL 1 (1.1) * OpenGL 2 (2.0) * OpenGL 3 (3.0) * OpenGL 4 (4.0) Renderer init order: 1) OpenGL 4 (4.0) 2) OpenGL 3 (3.0) 3) OpenGL 2 (2.0) 4) OpenGL 1 (1.1) Using renderer: OpenGL 4 (4.0) Shader versions supported: 110 to 400 Enabled Features: 0x00000FDF: - GPU_FEATURE_NON_POWER_OF_TWO - GPU_FEATURE_RENDER_TARGETS - GPU_FEATURE_BLEND_EQUATIONS - GPU_FEATURE_BLEND_FUNC_SEPARATE - GPU_FEATURE_BLEND_EQUATIONS_SEPARATE - GPU_FEATURE_GL_BGRA - GPU_FEATURE_GL_ABGR - GPU_FEATURE_VERTEX_SHADER - GPU_FEATURE_FRAGMENT_SHADER - GPU_FEATURE_PIXEL_SHADER - GPU_FEATURE_GEOMETRY_SHADER - GPU_FEATURE_WRAP_REPEAT_MIRRORED I don't know... what info to give you.... I'm on an Aspire v17 Nitro, Black Edition laptop... everything works as intended. Are there specs I can look up that you need? My framerate stays at 60 fps, window resizes, fullscreens, etc properly. Corrupter head swings, and I can make Neon and Malice do the Lightswitch Rave successfully, if you get what I mean by that. Uhm, I'm running windows 8.1, and it runs perfectly fine like this, even when the laptop is on battery instead of power cord. So... yeah. That. My resolution on my screen is 1920 by 1080. I use a QWERTY keyboard, so everything works normally like in the description. Also if my laptop adds one more typo to this with that damnable wrist-sensitive touchpad I'm throwing it out a window.
AltairPL
Thank you :D
Stran
Available renderers: * OpenGL 1 BASE (1.1) * OpenGL 1 (1.1) * OpenGL 2 (2.0) * OpenGL 3 (3.0) * OpenGL 4 (4.0) Renderer init order: 1) OpenGL 4 (4.0) 2) OpenGL 3 (3.0) 3) OpenGL 2 (2.0) 4) OpenGL 1 (1.1) Using renderer: OpenGL 4 (4.0) Shader versions supported: 110 to 450 Enabled Features: 0x00000FDF: - GPU_FEATURE_NON_POWER_OF_TWO - GPU_FEATURE_RENDER_TARGETS - GPU_FEATURE_BLEND_EQUATIONS - GPU_FEATURE_BLEND_FUNC_SEPARATE - GPU_FEATURE_BLEND_EQUATIONS_SEPARATE - GPU_FEATURE_GL_BGRA - GPU_FEATURE_GL_ABGR - GPU_FEATURE_VERTEX_SHADER - GPU_FEATURE_FRAGMENT_SHADER - GPU_FEATURE_PIXEL_SHADER - GPU_FEATURE_GEOMETRY_SHADER - GPU_FEATURE_WRAP_REPEAT_MIRRORED my framerate hovers above and below at 480 , 960 at almost the same rate. F3 toggle works, F4 toggle works but i feel like the overall quality looks less brighter when i compare to using F3 toggle. Computer Specs: CPU: i7 RAM: 16GB VRAM: 7908 GPU: AMD Radeon (TM) R9 380 Series . other tech demo functionality works for all the keys i pressed.
AltairPL
While replying to dudman I remembered I forgot to address this issue. I'm pretty sure that F4 issue may be caused by the Display or graphics card driver setting. You could try changing desktop resolution to non-widescreen one to see what happens. F3/F4 keys are only for testing purposes - depending on the outcome of the tests we may use only one of them (most likely F3 one) or make it an option - internally switch between them will still go through the window stage.
AltairPL
Oh, and I'm pretty sure that F4 issue may be caused by the Display or graphics card driver setting. You could try changing desktop resolution to non-widescreen one to see what happens.
AltairPL
Thanks :D. Can you just tell how the keyboard works? Like described in the post or differently?
AltairPL
Thanks :D
dudman
Available renderers: * OpenGL 1 BASE (1.1) * OpenGL 1 (1.1) * OpenGL 2 (2.0) * OpenGL 3 (3.0) * OpenGL 4 (4.0) Renderer init order: 1) OpenGL 4 (4.0) 2) OpenGL 3 (3.0) 3) OpenGL 2 (2.0) 4) OpenGL 1 (1.1) Using renderer: OpenGL 4 (4.0) Shader versions supported: 110 to 400 Enabled Features: 0x00000FDF: - GPU_FEATURE_NON_POWER_OF_TWO - GPU_FEATURE_RENDER_TARGETS - GPU_FEATURE_BLEND_EQUATIONS - GPU_FEATURE_BLEND_FUNC_SEPARATE - GPU_FEATURE_BLEND_EQUATIONS_SEPARATE - GPU_FEATURE_GL_BGRA - GPU_FEATURE_GL_ABGR - GPU_FEATURE_VERTEX_SHADER - GPU_FEATURE_FRAGMENT_SHADER - GPU_FEATURE_PIXEL_SHADER - GPU_FEATURE_GEOMETRY_SHADER - GPU_FEATURE_WRAP_REPEAT_MIRRORED No particular issues besides the F4 widescreen option stretches out the image (Minor side note, I use a French AZERTY Keyboard)
Available renderers: * OpenGL 1 BASE (1.1) * OpenGL 1 (1.1) * OpenGL 2 (2.0) * OpenGL 3 (3.0) * OpenGL 4 (4.0) Renderer init order: 1) OpenGL 4 (4.0) 2) OpenGL 3 (3.0) 3) OpenGL 2 (2.0) 4) OpenGL 1 (1.1) Using renderer: OpenGL 4 (4.0) Shader versions supported: 110 to 440 Enabled Features: 0x00000FDF: - GPU_FEATURE_NON_POWER_OF_TWO - GPU_FEATURE_RENDER_TARGETS - GPU_FEATURE_BLEND_EQUATIONS - GPU_FEATURE_BLEND_FUNC_SEPARATE - GPU_FEATURE_BLEND_EQUATIONS_SEPARATE - GPU_FEATURE_GL_BGRA - GPU_FEATURE_GL_ABGR - GPU_FEATURE_VERTEX_SHADER - GPU_FEATURE_FRAGMENT_SHADER - GPU_FEATURE_PIXEL_SHADER - GPU_FEATURE_GEOMETRY_SHADER - GPU_FEATURE_WRAP_REPEAT_MIRRORED No issues or crashes
AltairPL
Keyboard layout: At this stage it is an unpolished crap ;). As I've said in the post though, keyboard handling is not set in stone and may change sooner or later. Considering there's basically no way to configure the keyboard input at the moment, I thought this will be better idea for now, since keys are in the same place for QWERTY, QWERTZ, AZERTY, etc. Source code: I don't want to go into details on this, but there's a lot of reasons why I don't want to make the code public. This may change with time, but it's distant future, relatively speaking. Issue tracker, on GitHub or anywhere else, will certainly come in handy, so I should probably start thinking about it at least. Issue 1: I get the feeling some GPU drivers may actually make things worse. That said, scale filtering method is hard-coded for now, but it will be a user setting at some point. Issue 2: This one is known, to me at least. Issue 3: It's kinda the other way around really, I think. Right hand side of the FPS counter, loosely called FPS cap/limit in the post, is in fact the cap of the game clock - most likely it will be set to constant 60 in the game proper, but for the tech demo it had to be variable to allow getting max attainable FPS. I am aware that there are better solutions for game/render update speeds, but this is one of those things I had to do with RPG Maker compatibility in mind, and I would very much like to change it to something better in the future. Issue 4: Good to know, thanks. This is one hell of a feedback, thank you very much :D.
AltairPL
Thanks :D
AltairPL
It most certainly is not a joke ^^
AltairPL
Patreon UI is really wonky sometimes, so I always write patreon comments in text editor and just paste it to comment box when it's ready... saves a lot of trouble and nerves. Anyway, thanks for the report.
lolred
As someone who uses a non-typical keyboard, a game not supporting my layout is an immediate sign that it's unpolished crap. Fine for a free online game, DEFINITELY NOT FINE for a paid game. AltairPL: would you be down to put your code on GitHub? Since we're paying for it, I'd like to get to tinker with it. At the very least you should open an issue tracker there. Specs: Surface Book 1 with GeForce 940M dGPU, 3000x2000 screen, 8GB RAM, Windows 10 Insiders build 15063.11. The demo works as expected, I'm getting >400FPS fullscreen. Issue 1: lot more blurry than the reference image. Issue 2: rendering doesn't stop when the game engine isn't visible. (This eats my battery.) Issue 3: the game clock (as demonstrated by the head pendulum thingy) is tied to FPS. VERY BAD. Issue 4: going in and out of full-screen mode screws with OS-level scaling. Repro: 1. Go to Settings -> System -> Display -> Scale and Layout, set "Change the size of text, apps, and other items" to 200%. 2. Open Chrome. 3. Open URGE demo. 4. F4 into fullscreen, F4 out of full screen. Expected behaviour: Chrome looks exactly the same. Actual behaviour: Chrome scaled down. Workaround: go back to settings and reset scaling. Renderer info: Available renderers: * OpenGL 1 BASE (1.1) * OpenGL 1 (1.1) * OpenGL 2 (2.0) * OpenGL 3 (3.0) * OpenGL 4 (4.0) Renderer init order: 1) OpenGL 4 (4.0) 2) OpenGL 3 (3.0) 3) OpenGL 2 (2.0) 4) OpenGL 1 (1.1) Using renderer: OpenGL 4 (4.0) Shader versions supported: 110 to 400 Enabled Features: 0x00000FDF: - GPU_FEATURE_NON_POWER_OF_TWO - GPU_FEATURE_RENDER_TARGETS - GPU_FEATURE_BLEND_EQUATIONS - GPU_FEATURE_BLEND_FUNC_SEPARATE - GPU_FEATURE_BLEND_EQUATIONS_SEPARATE - GPU_FEATURE_GL_BGRA - GPU_FEATURE_GL_ABGR - GPU_FEATURE_VERTEX_SHADER - GPU_FEATURE_FRAGMENT_SHADER - GPU_FEATURE_PIXEL_SHADER - GPU_FEATURE_GEOMETRY_SHADER - GPU_FEATURE_WRAP_REPEAT_MIRRORED
Cereliona
RendererInfo: Available renderers: * OpenGL 1 BASE (1.1) * OpenGL 1 (1.1) * OpenGL 2 (2.0) * OpenGL 3 (3.0) * OpenGL 4 (4.0) Renderer init order: 1) OpenGL 4 (4.0) 2) OpenGL 3 (3.0) 3) OpenGL 2 (2.0) 4) OpenGL 1 (1.1) Using renderer: OpenGL 4 (4.0) Shader versions supported: 110 to 400 Enabled Features: 0x00000FDF: - GPU_FEATURE_NON_POWER_OF_TWO - GPU_FEATURE_RENDER_TARGETS - GPU_FEATURE_BLEND_EQUATIONS - GPU_FEATURE_BLEND_FUNC_SEPARATE - GPU_FEATURE_BLEND_EQUATIONS_SEPARATE - GPU_FEATURE_GL_BGRA - GPU_FEATURE_GL_ABGR - GPU_FEATURE_VERTEX_SHADER - GPU_FEATURE_FRAGMENT_SHADER - GPU_FEATURE_PIXEL_SHADER - GPU_FEATURE_GEOMETRY_SHADER - GPU_FEATURE_WRAP_REPEAT_MIRRORED All functions worked correctly, no crashes, Processor: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz, 2501 Mhz, 2 Core(s), 4 Logical Processor(s) GPU: NVidia GeForce 640M Memory: 6GB Ram Ran at 60 fps in windowed, windowed fullscreen, and fullscreen.
Username159
You picked a bad day to upload a status update.
Olinn
all window and tech demo functionality worked as described.
Olinn
CPU: AMD Radeon A6-5400K APU with Radeon(tm) HD Graphics 3.60 GHz. [] RAM: 8,00 GB (7,46 GB usable) [] GPU: AMD Radeon HD 7540D [] VRAM: 4,00 GB
Olinn
i got no crashes and no error prompts.
Olinn
both full screen modes worked, though the non-window one stretched the image sideways on my 1920:1080 screen. also, swapping from one type of full screen mode to the other required going back into normal window mode as both F3 and F4 de-full-screened the tech demo regardless of which full screen mode was active.
Olinn
displayed FPS values started fluctuating at 480 FPS and never reached 600 FPS despite the frame rate obviously increasing.
Olinn
reference image and tech demo window (reference image on the left, tech demo on the right) i see no difference: <a href="http://imgur.com/a/W2a5T" rel="nofollow noopener" target="_blank">http://imgur.com/a/W2a5T</a>
Olinn
my single long comment feedback seems to not have gone through, so i'm going to break it up into separate comments. render info text: <a href="http://imgur.com/a/RMMmr" rel="nofollow noopener" target="_blank">http://imgur.com/a/RMMmr</a>
