Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+1)

Hey buddy, thanks for testing out the bug. This screenshot is exactly what I need.

If you haven't run the game since encountering the problem, can I get you to send over the Player text file? That would also help me figure out what's causing it.

To get to the file, you'll need to go type %appdata% in your search bar, click on the folder, then go to LocalLow -> Mackerel Sky -> At Skies Edge. The file should be pretty easy to spot. You can copy the entire log file and put it on https://pastebin.com/ then send me the link to the paste. 

Thanks!

Had to make a fresh bugged log since the last one was too big, which also may or may not have been the bugged run.  Hopefully this'll help.

https://pastebin.com/ukye4s7w

From what I can see, it didn't seem like you triggered that cascade of error messages in the console from that log. Did your audio still cut out?

It did.  I can try another run and wait about a minute before exiting out.

https://pastebin.com/4hWF04rZ

Took longer than expected.  So I did wait but the queue kept growing with no dialogue or captions coming out.  I then headed over to Ogre to see if the dialogue will continue and take out the line of tanks, nothing.  So I crashed the plane and exited out.

(1 edit)

I think I have nailed this problem down. Once a a voice line script finishes printing, it is supposed to 'arm'  the next script to play after a certain amount of time has passed. This is done through Unity's coroutine functions, and I suspect the problem is that in some circumstances (e.g. if your computer is under load) the coroutines aren't firing properly. I've modified the manager slightly to record the time the next script should be fired. Then it checks whether or not the current in-game time has gone over this flag before arming the next script, so it should run independently of any coroutine nonsense.

(1 edit)

I have a video with that bug happening, i needed some restarts to get, maybe restarting the mission makes this happens too?
Here the log too: https://pastebin.com/L4d1VhuM

Here the video: 

(2 edits)

I think the "AW"s and "GN"s might be related to the bug; the dialogues disappear right after some of them appear on the Script DEBUG