[Axem]

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!

[DefCynodont119]

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


[Axem]

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]

[DefCynodont119]

Alright! it's working now! (except for the extreme arcade but meh)

I will tell you how awesome it is once I finish it.

[Commander Zane]

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

[Axem]

Well, my bad on that one. I didn't think anyone would be grinding them all the way down into dust. Glad to hear you got past it anyway and super glad you really enjoyed yourself.

[tomimaki]

I got error messages in JAD 2.22 on nightly release build.
I'm guessing this line:

Code: [Select]

$Subsystem: turret14,1,0.8.0should look like this:

Code: [Select]

$Subsystem: turret14,0.8,1.0Funny thing, FSO 21 debug build sees nothing wrong with this line.

[Svedal]

I got error messages in JAD 2.22 on nightly release build.
I'm guessing this line:

Code: [Select]

$Subsystem: turret14,1,0.8.0should look like this:

Code: [Select]

$Subsystem: turret14,0.8,1.0Funny thing, FSO 21 debug build sees nothing wrong with this line.

There's something quite similar to this with FSport as well--had a 0.1.5 somewhere in weapons.tbl. Works before a certain nightly, not afterwards.

Asteroth suggested maybe float parsing has changed and thus is no longer making sense of nonsense.

[Betamatcen]

I was playing the JAD Trilogy and the JAD 2.2 series on the latest version of FSO (using Knossos)
and I noticed a lot of glitches and oversights that should probably be fixed.
I cataloged these following issues:


JAD

Level 2:
 
When the Colossus crashes into the Sathanas, it creates a bunch
of shockwaves that last a very long time, are too slow, and is very hard to
look at due to the bright light from the shockwaves.

JAD3:SoaP

Level 6:

A extra cutscene is supposed to trigger if the player does not escape
the supernova on the way to the Knossos, or get killed by FRED
but does not get called. Here is the cutscene:
 
https://www.youtube.com/watch?v=wgmuDtQlTLY

JAD2.21

Fly like you want to win:

The race against Delta 1 is way too rigid, and a single mistake can
make you fail the mission. There should be more room for error.
(Maybe decrease Delta 1's speed?)

JAD2.22

Meet cute:

When the Sentinels start shooting beams at you, if they hit you
they do a CRAZY amount of damage, and can kill you in like 3 hits
regardless of difficulty! Playing this level on easier difficulty levels
does not help at all! This makes the level VERY hard and frustrating!
It should probably be dialed back in the damage department.
I had to use cheats just to beat this level! (And I play on Very Easy!)


Just on the side, I think the cutscenes for JAD3:SoaP should be in
the tech room to watch including the unused cutscene. (See above for
info on cutscene in question.)Also, the 42nd Hitchhikers squad insignia
does not show up in the insignia list, of all the insignias there is one that
seems to not be visible, instead there is a blank slot. I assume that's supposed
to be the insignia for JAD.


These are all the glitches and oversights I could find during my playthrough.
It would be nice if these could be fixed.

Thanks!

[Boomer20]

I'm getting a bug in JAD 2.23 where I am now constantly dying with the reason being "*player* was killed by collision with player one."

The first time it happened just after I collided with

Spoiler:

Henrietta (as a light ball with less than 35%) while she was beaming.

Subsequent retries just have me dying almost instantly or when I get to the same point as I was at.

I've attached a log but I don't know if it will help or not.
Also JAD 2.23 seems to spew a few errors on mission loading.