Old issue #180/#204 has resurfaced - Infinate "Initializing Ren'Py static data..."
Savage1969 opened this issue ยท 14 comments
I searched and did not find this issue open in the current build. This was resolved in the past but has suddenly resurfaced in every project. Please advise.
Edit: This issue is the occurrence when opening a project outside of the SDK (which many of us do).
Edit2: Now that 2.3.1 was pushed it does this in the SDK as well. It's completely broken now and causes other issues such as "Find in Files" impossible since the process never ends.
If this is a duplicate of a currently reported issue I didn't notice then please move this where appropriate. Regards.
I'll look into it tomorrow, I remember some having this issue on the development branch but not on the main branch. Might be a configuration issue.
Ah, actually seems like it was the opposite in #180. I'll still make an attempt to test it tomorrow, see if I cn trigger the issue myself
Would you be able to compile a minimal project where this issue occurs? Easiest is probably grabbing a copy of a project that is broken and stripping everything that you don't want to upload. (You can also send me the zip file privately is that's preferred)
Having a project where it fails will help me figure out the issue much faster than going at this blind
Hi there, I made a new build (v2.3.2). I added a logging output category for the extension to hopefully get some answers about what is going on here. Could you please post the log from the project you're having issues with? You can find it here:
Apologies for the late reply, I did not see your new post. Otherwise I do not have that category available to me:
@Savage1969 Are you using the pre-release version?
@LuqueDaniel I tried it in both v2.3.3 and in v2.3.2 (as originally directed), neither have the category on my end.
Edit: For what it's worth I get many more category options in v2.1.7 after the static info builds... so maybe it's due to that stuck process in the later versions. Just a hunch.
Here's the same view in v2.1.7 after the static info builds. Notice the category vertical scroll bar due to the extra categories:
Sounds to me like the extension is crashing which is causing all the issues. Basically once it crashes it will not do anything.
So help me help you :). I can't reproduce any of the issues you are facing. I downloaded the new Ren'Py 8.1.1 SDK to make sure I have the latest tutorial game project.
Then I downloaded the lastest pre-release version (v2.3.3) to my vscode installation.
Note that I'm NOT using the installation that comes with the SDK, but my already pre-installed vscode. (My vscode version is 1.79)
Now I did not run the tutorial game yet, meaning the game is not compiled. Using the Ren'Py SDK, I then pressed the 'Open Project' button.
Then I clicked the tutorial_atl.rpy file.
This is what I see then:
At the bottom of that image, you can also see the Ren'Py language extension logs. You can see that it does not find the navigation.json, yet it functions properly. As you can see, I'm not facing the same issues, so I'm kinda lost here. Could you help me figure out what triggers your issue?
Are you doing anything different from the steps I just described?
Are you using a custom Ren'Py SDK?
Did you make any changes to the settings in the SDK?
Are you seeing any other errors popup during startup?
I'm running into the same issue. Infinite "Initializing Ren'Py static data..."
The pop up below flashes for a split second (sorry for the screen grab quality, had to use my phone camera since it was flashing too fast):
Dollars to doughnuts if you revert back to v2.1.7 you won't get the static data build issue. Test that and confirm. To do this (if you don't know), click the drop arrow next to "uninstall" (to open the context menu) and select "Install Another Version".
So help me help you :). I can't reproduce any of the issues you are facing. I downloaded the new Ren'Py 8.1.1 SDK to make sure I have the latest tutorial game project.
...
...
At the bottom of that image, you can also see the Ren'Py language extension logs. You can see that it does not find the navigation.json, yet it functions properly. As you can see, I'm not facing the same issues, so I'm kinda lost here. Could you help me figure out what triggers your issue?Are you doing anything different from the steps I just described? Are you using a custom Ren'Py SDK? Did you make any changes to the settings in the SDK? Are you seeing any other errors popup during startup?
In that scenario of running the demos in any version of the SDK, yes, it functions correctly for me (including log output) even though I open projects in VSC outside of the SDK. In my previous posts the screen examples of the Output window were to show that during the static build hang that the Categories do NOT complete to give you some context that once it hangs, it appears that there's some portions of the VSC init phase that cannot progress further as well.
My VSC is one installation outside of any SDK (as most folks likely have) just as you described. I don't change any settings in any of the SDK's (I only use the SDK for building, not opening projects nor launching them) and use them from v7.3.5 to v8.0.3 currently over dozens of projects. The static issue occurs across the board regardless of RenPy version. Again, I (and many folks working on a gamut of projects over various versions of RenPy) open projects outside of the SDK but with that said I've tried copying those projects inside the appropriate SDK base directory and opening within the SDK with the same static build not completing issue.
When the static build issue occurs there are no popup errors but it's becoming obvious that since it gets hung on that process that the rest of the VSC init does NOT occur which is why the Output categories, etc are not completed during this circumstance.
To be clear the issue does NOT exist when reverting back to v2.1.7 although other issues occur like colorization due to it being a non-updated build (obviously). But once in v2.1.7 one can then at least perform basic tasks such as search/find across the entire project once again, have all the other installed extensions function correctly, and survive to work on the project(s). I'll imagine I'll have to find a way to strip down one of these massive private projects into something I can offer you as I'm a collaborator and not the contents owner per se.
Please try v2.3.4 this issue is likely fixed in that build :)
@duckdoom4 ... it took a long time to build (in the project I have open which is huge) and I almost gave up after a few minutes but it finally completed:
That's with v2.3.4 which, since VSC could now finish it's init phase has seemed to cure many of the other extensions that were displaying as failed as well (I haven't check them all yet though).
Thank you. I can now hopefully work once again without the massive struggle that was starting to impede my deadlines. Brilliant work sir. Please don't forget this secret sauce for the next major update (j/k).
You can close the issue if you wish but maybe give us 24hrs or so to insure it's all okay. Again, I've only tested on one project at the moment.
Alright, I'll close it. You can always reopen the issue if something else pops up