Jump to content


Renalr

Member Since 13 May 2018
Offline Last Active Jun 24 2018 12:34 AM

Posts I've Made

In Topic: MO3.3 SUPPORT // Game or Client Crashes & Launch Issues Megathread

23 May 2018 - 04:29 PM

Except.txt is in the snapshot folder. You should look for the one with the name that represents the timestamp of the crash

Snapshot should be in the Mental Omega directory, and not in some other place, right? My Mental Omega directory doesn't seem to have a snapshot folder. Looking in the debug directory, it's just debug.log files.


In Topic: MO3.3 SUPPORT // Game or Client Crashes & Launch Issues Megathread

23 May 2018 - 02:37 AM

Yeah, you're not meeting the post quota for upload permission.

You might be able to try posting link with a file-hosting website

You can also change it to a .txt and it will go through.

 

 

Could you also take a look at these? Let me know if there are additional files I should upload.

The except.txt from that crash could be useful, because the syringe.log doesn't show any information about this crash.

(For reference: Syringe outputs data for one crash, and there already was a VBB issue.)

 

Unfortunately the crash doesn't seem to have produced an except.txt. I reproduced the crash but each time it's just a generic Windows 10 "Yuri's Revenge has encountered an error and needs to close" with the buttons "Debug" and "Close."  I don't know if the debug.log will help but here it is: Attached File  debug.txt   9.32KB   45 downloads

I can provide a save file with the necessary conditions to induce the crash and the instructions to do so if needed.


In Topic: MO3.3 SUPPORT // Game or Client Crashes & Launch Issues Megathread

19 May 2018 - 04:24 AM

I have two issues to report (running on Windows 10).

On Foehn Mission 2 Kill the Messenger, I had a whole bunch of ivan bombs and bloaticks detonate, along with a bunch of foxtrot missiles concentrated in a small area. This left behind a whole bunch of fire/toxic gas particles, and when I tried to load a different save or quit the game, it crashed to desktop. syringe.log is attached. attachicon.gif syringe.txt

 

The other problem is starting Final Omega from the game client. If I click on the button "Map Editor" nothing happens, and no error or window pops up. I couldn't find any log file related to this. MentalOmegaClient, FinalAlert2MO, and the syringe inside the Map Editor directory are all set to "Run as administrator." Additionally, FinalAlert2MO is set to run in compatibility mode for Windows XP SP3.

Could you also take a look at these? Let me know if there are additional files I should upload.


In Topic: MO3.3 SUPPORT // Game or Client Crashes & Launch Issues Megathread

13 May 2018 - 07:36 PM

I have two issues to report (running on Windows 10).

On Foehn Mission 2 Kill the Messenger, I had a whole bunch of ivan bombs and bloaticks detonate, along with a bunch of foxtrot missiles concentrated in a small area. This left behind a whole bunch of fire/toxic gas particles, and when I tried to load a different save or quit the game, it crashed to desktop. syringe.log is attached. Attached File  syringe.txt   18.84KB   79 downloads

 

The other problem is starting Final Omega from the game client. If I click on the button "Map Editor" nothing happens, and no error or window pops up. I couldn't find any log file related to this. MentalOmegaClient, FinalAlert2MO, and the syringe inside the Map Editor directory are all set to "Run as administrator." Additionally, FinalAlert2MO is set to run in compatibility mode for Windows XP SP3.