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

0 Members and 1 Guest are viewing this topic.

Offline Axem

  • Administrator
  • 211
Re: Just Another Troubleshooting Thread
Also forgot to mention...

Thanks. After I got past that point, there were no more problems. Man, I was way off about that being the final boss fight.

Really great campaign. I know I've been all complaints so far, but I enjoyed the campaign a great deal. The next time I'm introducing someone to FS2, I'm going to point to JAD as an example of how far the community has pushed the engine to do things it was never intended to do (as well as it just being very entertaining).

I'm glad that worked out! And I'm even more glad you really enjoyed it! :)

 

Offline DefCynodont119

  • 29
  • I should put something witty here- but not this. .
    • Steam
Re: Just Another Troubleshooting Thread
OK, finely got around to installing, I put all the VPs in one mod folder and jad2.1 and 2.2 work fine, but 2.3 gives a blank screen and crash in the campaign room and extreme arcade (incorrectly) says my screen res is too low. .

(I have 1280x1024)

I would post the whole log file, but um I can't seem to create one. . . .   which has never happened before and is terrifying in it's own right. .



Code: [Select]
Assert: "handle >= 0"
File: bmpman.cpp
Line: 110
Invalid handle -1 passed to bm_get_slot!

ntdll.dll! ZwWaitForSingleObject + 10 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 156 bytes
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 13 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes

[ This info is in the clipboard so you can paste it somewhere now ]


Use Debug to break into Debugger, Exit will close the application.

ntdll.dll! ZwWaitForSingleObject + 10 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 156 bytes
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20191212_da1634c_x64_SSE2-FASTDBG.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 13 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes
My gift from Freespace to Cities Skylines:  http://steamcommunity.com/sharedfiles/filedetails/?id=639891299

 

Offline Axem

  • Administrator
  • 211
Re: Just Another Troubleshooting Thread
Ugh, I forgot to commit the file so it never got in the update. AAAAAAAAAAAAAAAAAAHHHHH

So take the attachment and throw it in yourjad223folder/data/interface and you should get a mainhall. Just a little clipped.

Also I'd recommend to use FSO 19.0 RC2. It was released on Dec 24 and its a bit newer than your nightly.

[attachment eaten by a Shivan]

 

Offline DefCynodont119

  • 29
  • I should put something witty here- but not this. .
    • Steam
Re: Just Another Troubleshooting Thread
Alright! it's working now! (except for the extreme arcade but meh)

I will tell you how awesome it is once I finish it.
My gift from Freespace to Cities Skylines:  http://steamcommunity.com/sharedfiles/filedetails/?id=639891299

 

Offline Commander Zane

  • 212
  • Spoot Knight of Anvils
Re: Just Another Troubleshooting Thread
Since I got my new rig set up and everything configured again for FS2, I got back to JAD and figured out what was going on in Neon Genesis Volition.

Previously, I wasn't able to complete the mission because:
Spoiler:
When attacking Crunchr Team, the bridge subsystem must be destroyed to allow for directive progression. On previous attempts, I just took the time to Progressive Chainsaw them to death which are not considered mission kills.

It could be my fault for using such brutish tactics, but I figured out how to continue progressing and reached the end. Absolutely incredible way to end JAD, absolutely incredible mod from beginning to end, and thanks for the shout-out! <3

  

Offline Axem

  • Administrator
  • 211
Re: Just Another Troubleshooting Thread
Well, my bad on that one. I didn't think anyone would be grinding them all the way down into dust. :nervous: Glad to hear you got past it anyway and super glad you really enjoyed yourself. :)