Error in frame: array::at: __n (which is 8) >= _Nm (which is 6)
Error in frame: array::at: __n (which is 8) >= _Nm (which is 6)
Hello guys, in OpenMW 0.47 I got an error messages "Error in frame: array::at: __n (which is 8) >= _Nm (which is 6)" at a certain point around 10 minutes into the total conversion Myar Aranath. But in version 0.45 this doesn't happened. So I guess it seems to be related with shadows and texture mapping. However, even when I disable all shaders and maps settings in the settings file of 0.47 the error persists. Any ideas what could cause the problem? Is it due to Myar Aranath being outdated from 2005? Thanks.
Re: Error in frame: array::at: __n (which is 8) >= _Nm (which is 6)
I checked again, in OpenMW 0.46 Myar Aranath also works. It just don't work with OpenMW 0.47. In the windows version of 0.47 the error message is "Error invalid array <T, N> subscript". Hope this helps.
- psi29a
- Posts: 5361
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: Error in frame: array::at: __n (which is 8) >= _Nm (which is 6)
Same with a daily development build?
- AnyOldName3
- Posts: 2677
- Joined: 26 Nov 2015, 03:25
Re: Error in frame: array::at: __n (which is 8) >= _Nm (which is 6)
Do you have any actual reason to think it's shadows-related, or is it a random guess?
Re: Error in frame: array::at: __n (which is 8) >= _Nm (which is 6)
Hi, I also tried with the nighty build 0.48 a while ago, but same error. I just tried the new developement version again, but it is not usable under my Debian Testing. I got the error message "boost::filesystem::directory_iterator::construct: Call not implemented [system::120]: "C:\OpenMW_MSVC2019_64_RelWithDebInfo_master/./resources\vfs", although Visual C++ redist 2005 to 2019 are all installed under wine64-6.23 .
Just a pure guess, but advanced shadows and extra lighting settings were introduced with 0.47. I first thought the Nm in the error message means normal maps, but setting them to false in the settings.cfg did not help either.
Just a pure guess, but advanced shadows and extra lighting settings were introduced with 0.47. I first thought the Nm in the error message means normal maps, but setting them to false in the settings.cfg did not help either.
- AnyOldName3
- Posts: 2677
- Joined: 26 Nov 2015, 03:25
Re: Error in frame: array::at: __n (which is 8) >= _Nm (which is 6)
Why are you using a Windows build on Debian? Use a Debian build. Call not implemented sounds like exactly the kind of thing that could be caused by a Wine issue.
Re: Error in frame: array::at: __n (which is 8) >= _Nm (which is 6)
Thank you AnyOldName3,
After digging around I found out that the 0,49 build for Linux from today under https://redfortune.de/openmw/nightly/?C=M;O=D worked. However the 0.48 build from 15.07. does not work, it has the same error as the official Linux build 0.47.
After digging around I found out that the 0,49 build for Linux from today under https://redfortune.de/openmw/nightly/?C=M;O=D worked. However the 0.48 build from 15.07. does not work, it has the same error as the official Linux build 0.47.