Author Topic: Just Another Troubleshooting Thread  (Read 142340 times)

0 Members and 1 Guest are viewing this topic.

Re: Just Another Troubleshooting Thread
Seems to be working now, thanks man!

 

Offline Axem

  • Moderator
  • 211
Re: Just Another Troubleshooting Thread
Nice :yes:

 
Re: Just Another Troubleshooting Thread
I seem to be running into the same issue as hack-wizard.  On the first VN sequence of the game it has an error and can't find certain files like title_holleyB, title_holleyA, title_MervB, etc.
https://pastebin.com/vG4rZbvQ

 

Offline Axem

  • Moderator
  • 211
Re: Just Another Troubleshooting Thread
Are you using the version on Knossos or from the FSO Installer? Knossos should work but I haven't updated the Installer files yet (will be doing that tonight!)

EDIT: (Actually I can see from your debug log its the installer, so hang tight!)

 
Re: Just Another Troubleshooting Thread
Thanks for the reply.  If i get impatient enough I may try out Knossos.  Looks all fancy and posh.

 

Offline Axem

  • Moderator
  • 211
Re: Just Another Troubleshooting Thread
Yeah, it's a wonderful program! Super easy to get stuff installed and uploaded. Its just a bit of a shame that you need to basically redownload all your past mods, but atleast user data is still saved.

Anyway, FSO Installer files now updated!

 

Offline CT27

  • 211
Re: Just Another Troubleshooting Thread
I PMed Axem about this but I'll ask here too in case anyone has any ideas:

I ran the FSO Installer recently to see if there were any updates for any of my campaigns and I had a problem with JAD 2.21.  I got this message:

"The following error was encountered:

Just Another Day 2.21:  You Are Not Alpha 1:  The has value for 'jad221_root.vp' did not agree with the expected value.  This could indicate a corrupted download or a problem with the mod.  If this problem persists over multiple attempts, contact the mod author for assistance.  The file has been deleted'


Up until I tried this today I haven't had any technical problems with JAD 2.2 campaigns.

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Just Another Troubleshooting Thread
...And when you ran the installer again, did it happen again?
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline CT27

  • 211
Re: Just Another Troubleshooting Thread
...And when you ran the installer again, did it happen again?

Yes, I ran the Installer a few times in a row, and each time the cycle repeated.  It downloaded the 'root' file for 2.21 but then it gave that error message and after a while of the top line saying 'computing hash values' the top line icon for 2.21 on the Installer had the red dot light up after a minute or two each time.  When I went to the next screen I saw that error message I posted.


However, I encountered a unique work around.  I ran the Installer again...after the root file was finished downloading it went to the computing hash values phrase...before it was finished with that phase of the installation I hit 'cancel' on the Installer.  I looked in the JAD 2.2 folder and I had the 'root' file for 2.21 without getting that error message on the Installer.  I loaded up the campaign and I was able to play JAD 2.21 now.

 

Offline Axem

  • Moderator
  • 211
Re: Just Another Troubleshooting Thread
Weird, the jad221 root md5 doesn't match with the installer file. Maybe I forgot to update that one from a previous version. I'll fix it tomorrow.

 

Offline Axem

  • Moderator
  • 211
Re: Just Another Troubleshooting Thread
Okay, the file hash should be fixed now.

  

Offline CT27

  • 211
Re: Just Another Troubleshooting Thread
Okay, the file hash should be fixed now.

It worked.  Thank you.

 

Offline JSRNerdo

  • [`_`]/
  • 29
  • Gone!
Re: Just Another Troubleshooting Thread
Playing Cowboy Delta Star on the latest nightly, I managed to blow up Holley's ship after making the -hojo fighters run away and before the doge.

I can't believe Holley is now dead and is haunting Command to send messages
Former Inferno lead, BTA fredder-ish and DE fredder. Driven out by ordinary fascists the_e, aesaar and general battuta. Will return if they're ever removed.

 

Offline Axem

  • Moderator
  • 211
Re: Just Another Troubleshooting Thread
Murderer.

I'll have you summarily executed for this.

 
Re: Just Another Troubleshooting Thread
Speaking of Cowboy Delta Star, it seems that GM Holley's secret weapon is powerful enough to destroy reality.
...or the beginning of the boss fight is causing the game to crash.  Could be either, tbh.

Code: [Select]
ntdll.dll! NtWaitForSingleObject + 20 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 162 bytes
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_AVX-FASTDBG.exe! <no symbol>
KERNEL32.DLL! BaseThreadInitThunk + 20 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes
Same results with the most recent 3.8.1 nightly.

And here's the fs2_open.log to go with the above error message.

EDIT: Almost forgot to mention that I'm using Knossos.
« Last Edit: July 06, 2018, 11:05:06 pm by TheLocalTechPriest »

 

Offline Axem

  • Moderator
  • 211
Re: Just Another Troubleshooting Thread
We thank the Adeptus Mechanicus for reporting this manifestation of chaos. By the Emperor's grace, it will be purged.

 

Offline Axem

  • Moderator
  • 211
Re: Just Another Troubleshooting Thread
The heresy has been purged and a new update will be dropped tomorrow.

That issue will be fixed, along with an assortment of other small and mostly harmless (but still annoying) things.

 

Offline Spoon

  • 212
  • ヾ(´︶`♡)ノ
Re: Just Another Troubleshooting Thread
Omnissiah be praised, the warp corrupted POOCHIE's have been terminated.
Urutorahappī!!

[02:42] <@Axem> spoon somethings wrong
[02:42] <@Axem> critically wrong
[02:42] <@Axem> im happy with these missions now
[02:44] <@Axem> well
[02:44] <@Axem> with 2 of them

 

Offline Axem

  • Moderator
  • 211
Re: Just Another Troubleshooting Thread
Knossos has the update now. FSO installer will get it later in the day.

 
Re: Just Another Troubleshooting Thread
May the Omnissiah's blessings be upon you.