Runtime error index out of range

[roswellguitar]

Hello,

I tried launching the exe and got this error message when launching. I changed the config file to get the journal where it should find it. Do you have any idea where it could come from?

This is the result with --log debug

[RBracy]

Could you paste the contents of your config, also?

[roswellguitar]

journalsfolder: "E:\Saved Games\Frontier Developments\Elite Dangerous"
refreshratems: 1000

[roswellguitar]

that's my conf.yaml if that's what you asked for?

[RBracy]

Let me get some clarity. Are you using single or double backslashes in your path name? I attempted to insert some text to recommend you use two, and GitHub automatically made them single when my comment posted.

[roswellguitar]

i'm having double backslashes
i didn't even realized it deleted them on the post

[roswellguitar]

tried with only one backslashes and it's worst, idon't even have the command windows staying. it pops in and out immediately

[peterbn]

Hi - sorry for not responding earlier.

You shouldn't really need to change the conf.yaml file. The default value should work. Have you tried with the default value?

journalsfolder: "%USERPROFILE%\\Saved Games\\Frontier Developments\\Elite Dangerous"

As for the command window not staying open, you can try to open a command line manually, navigating to where you have unzipped the tool, and then run the program.
That way, the command window will stay open even if the program crashes.

You can also try running it with --log trace to see the exact file it tries to read. That might give more information about what's going wrong.

[roswellguitar]

Hello Peter, Problem is that my user is on drive E: and when using the default value it's trying to get the All tries : *-FIRST TRY * with config: journalsfolder: "E:\\Saved Games\\Frontier Developments\\Elite Dangerous" refreshratems: 1000  *-SECOND TRY* with config: journalsfolder: "E:\Saved Games\Frontier Developments\Elite Dangerous" refreshratems: 1000  *-THIRD TRY* with default config journalsfolder: "%USERPROFILE%\\Saved Games\\Frontier Developments\\Elite Dangerous" refreshratems: 1000  Best regards, Maël

…

[peterbn]

Hello Maël,

Sadly, the images did not make it through to the bug tracker from your email. Would you mind logging in to github and adding them directly?

[roswellguitar]

Oups sorry, i updated my last post, tell me if it's not working

I'm wondering : does the journal logs have changed since odyssey update?

[peterbn]

not sure - I don't have Odyssey... Do you see files named Journal.*.log in either of the folders you tried? (* is a long sequence of numbers)

[roswellguitar]

Yes

[peterbn]

Ok - Odyssey may be an issue, if it adds journal lines that I'm not considering.

Would you mind compressing the entire folder as a zip and attaching it here? That should let me try to reproduce later today.

[roswellguitar]

Elite Dangerous.zip

[roswellguitar]

Thanks for all your quick answers 👍 that's really kind of you!

[peterbn]

Not a problem - the zip file appears to be broken. I cannot open it with standard unzip tools :(

Can you open it yourself?

[peterbn]

Hi - were you able to create a new zip file? The old one appears to be corrupted.

[Voodoo-le-Strange]

I don't know if this is exactly the same problem, but I mentioned the issue about a Runtime Error: Slice Bounds Out of Range happening since the last Odyssey patch 5 was released. I mentioned in to Cmdr pakkenberg on the Elite: Dangerous PVE forum and he suggested I uploaded the journals.

So I have attached a screenshot of the error message, and uploaded the journals folder with the last couple of months files in it.

Hope this helps.

Elite Dangerous.zip

[roswellguitar]

Hello Peter,

Sorry for not ansering i was away this week-end. It seems i can open the .zip i gave in my last comment but i'm uploading it again.
Thanks Voodoo for your feeback! :)

Elite Dangerous.zip

[peterbn]

Thanks for the zip file Voodoo.

Maël, yours is still broken for some odd reason, but I'll see if I can't resolve the issue with what I got from Voodoo.

Completely unrelated, should I buy Odyssey? Is it worth playing?

[Voodoo-le-Strange]

This is a purely personal opinion, but Odyssey is fundamentally flawed compared to Horizons. Even after 5 major patches (which is pretty much all FDev have said they're doing until the console release in 6 months time) the lighting remains bad (too dark generally), the frame rate performance in stations is bad (so you have to brute force your frame rates with high end hardware or turn down quality to compensate), and they have a major problem with new planets surfaces being made up of custom tiling rather than procedurally generated as in Horizons (the issue with the tiling is that new planets have become quite bland and the tiling too often repeats noticeably).

Personally, I think they have focused too much on getting the First Person Shooter aspect of the game, and the planetary atmospherics looking good at the expense of too many other things. Gaming websites are advising not to purchase the game until the console release...in the hope that Frontier have fixed all the flaws by then. I myself have gone back to Horizons, although most of my squadron are just braving it out.

As I say, just my take on it, but the disappointment is echoed by many big-name influencers like Obsidian Ant and Down To Earth Astronomy, etc.

[peterbn]

Voodoo, check out https://github.com/peterbn/EDx52display/releases/tag/v1.3.2. Turns out your issue probably didn't have anything to do with Odyssey. It was "just" a bug in shortening the planet names by removing the system name that didn't correctly consider "Leesti" in the "Leesti" system.

Maël, you can try the release above as well to see if it solves your problem, but if it doesn't I do need a new zip file from you - or a .tar.gz or some other archive. I don't know what software you are using to create zip files, but could you try something else? I cannot open the second one you attached either. Let me know if you need suggestions for compression software.

[Voodoo-le-Strange]

I can confirm that the "Slice Bounds Out of Range" issue is now fixed in v1.3.2.
(Obviously just a complete coincidence me arriving in Leesti at the time the Odyssey patch dropped).

Thank you very much for fixing, Peter. All the best.