[chief1983]

Did you follow the instructions I mentioned in a post in that mod's release thread?  There were some missing files I packed together later, and I had re-exported the models to fix some collision errors.

[Dragon]

I'm well aware of this ,I'm trying to get this mod to work ,so I was expecting it.
Now I want to fix it ,that's all.

[chief1983]

I just wanted to make sure you weren't redoing work I'd already done.  The stuff I had released didn't really have any errors left when set up properly.

[Dragon]

OK ,nevermind BSG ,I got a problem when using BTRL warpout with high-speed fighter.
Debug build CTD ,I though there won't be any after you helped me solve the texture assertion.
Log ends with this.

Code: [Select]

Player lethality: -10.0, num turrets targeting player: 0
Got event GS_EVENT_PLAYER_WARPOUT_DONE_STAGE1 (44) in state GS_STATE_GAME_PLAY (2)
Hit target speed.  Starting warp effect and moving to stage 2!
Int3(): From E:\Storage\FSO\fs2_open\code\Render\3dSetup.cpp at line 561

Effect is directly from BTRL ,as well as code.
Fighter was mowing at around 300m/s ,I would like to increase it.
(it was completely awesome flying it ,swithing glide on and off and shooting bullets that inherited my velocity. Newtonian dampening was also on.)
I'm sorry for posting so many strange ,hard to repeat errors ,this one (fortunately? ) is repeating every time I want to use new warpout.
As always I fly black Steve'o's Lancer ,though it repeated on black Jacal.
EDIT: Ship slowed down to 140m/s at warpout from over 600m/s max (without burners)
The error still happens.
EDIT2: One more info: this is caused by warp effect or departure itself.
When I ordered wingmen to depart the same thing happened.
Toggling 3D warp doesn't matter.

[Wanderer]

Error seems to indicate the clipping plane normal is not of proper length. The actual mod data is required for the data to be debugged

[karajorma]

The BtRL warpout doesn't work in 3.6.10. The problem is only fixed in 3.6.11.

[Dragon]

So I need to disable the warpouts?
OK ,I will comment them out and enable as soon as you release 3.6.11 build.
Unfortnately the only getable 3.6.11 is unstable (you call it HEAD as I recall) ,right?
Is there any way I can assist in development?
I like using things in unusual way ,so maybe I can help you with bugfixing.

[karajorma]

Any of the nightly builds that have appeared in the last couple of weeks are 3.6.11 branch, but don't go back more than a couple of days if you want working warpouts as the code wasn't committed until then.

The best way to help with bugfixing is to report bugs on Mantis and be available when they are updated. I've lost count of the number of bugs sitting around cause no one pays attention when a coder finally does have time to work on them and posts a question.

[FreeSpaceFreak]

What does this one mean? (3.6.10RC2)

Code: [Select]

ASSERTION: "sip->subsystems[j].model_num == sip->model_num" at Ship.cpp:15695


[Wanderer]

Where exactly do you encounter that assert? Which mod, which models?

[FreeSpaceFreak]

Mod Ancient-Shivan War, support ship.

[Wanderer]

Hmm.. Make sure all the subsystem data in model file and in the tables match. Both names and the number of the subsystems.

[Dragon]

I'm back ,again with debug CTD.
It happens on an explosion of reskinned Cutter (textures from INFA).
The last lines of the log:

Code: [Select]

Player lethality: 109.8, num turrets targeting player: 2
AI ship is seeking lock
Player lethality: 109.6, num turrets targeting player: 3
Loaded Arc_04.wav
Player lethality: 109.5, num turrets targeting player: 2
Player lethality: 109.3, num turrets targeting player: 2
Player lethality: 109.2, num turrets targeting player: 2
Player lethality: 109.1, num turrets targeting player: 2
Player lethality: 108.9, num turrets targeting player: 2
Player lethality: 108.8, num turrets targeting player: 2
Loaded boom_1.wav
Loaded clusterboom.wav


It's most likely a model error ,textures doesn't even include my rotated Fen05.
This model isn't causing problems anywhere else.

[Wanderer]

Impossible to tell as there nothing immediately apparent in the log.

Do you get any warnings when starting the game, or does the full log contain any warnings?

[FreeSpaceFreak]

Hmm.. Make sure all the subsystem data in model file and in the tables match. Both names and the number of the subsystems.

Yes, that  was it. The nav subsystem was in the table, but not on the model. Thanks.

Strangely enough, it now does a CTD when it's finished loading the mission...

* FSF heads into log

[Wanderer]

Create empty text/ASCII file named 'debug_filter.cfg' to the same directory where the log file is created to. Run the debug build. Exit the game. Open the log file (this time a tad longer file). Then post only the ten (10) last lines or so from it.

[Dragon]

Impossible to tell as there nothing immediately apparent in the log.

Do you get any warnings when starting the game, or does the full log contain any warnings?

No ,there are no problems until the breakup moment.

[FreeSpaceFreak]

Create empty text/ASCII file named 'debug_filter.cfg' to the same directory where the log file is created to. Run the debug build. Exit the game. Open the log file (this time a tad longer file). Then post only the ten (10) last lines or so from it.

I got one... Last lines of the FS2_Open.log:

Code: [Select]

Received post for event GS_EVENT_START_BRIEFING during state transtition. Find Allender if you are unsure if this is bad.
Got event GS_EVENT_START_BRIEFING (15) in state GS_STATE_START_GAME (52)
No briefing music is selected, so play first briefing track: ASW Briefing 1
AUDIOSTR => Successfully opened: Ancients_Briefing.ogg
ANI 2_BriefMap with size 918x400 (21.9% wasted)
Entering brief_init()
entering common_select_init()
ANI iconwing01 with size 32x28 (12.5% wasted)
Int3(): From E:\Storage\FSO\fs2_open\code\MissionUI\MissionShipChoice.cpp at line 3507

[Wanderer]

Dragon...

To solve your issue i need the data you are using (models, textures, tables, effects, missions, teh works). And then try to reproduce the issue with debugger attached.



FreeSpaceFreak...

Make sure that the icons you have defined for the ships are valid in ships tables (tbl/tbm's '$Ship_icon:' entry) or then try using the 'use models for ship selection' option from the launcher.

[FreeSpaceFreak]

Using models for ship selection did the trick, thanks.