[Wanderer]

Dunno what purpose \n\ and ""\ serves...

They are notations for newline etc. Please do not include them into your table files.

EDIT: Also \" should be just " in the table files.

[chief1983]

Code: [Select]

#Ship Types

$Name:                  Fighter
+nocreate
$Turrets prioritize ship target: NO

$Name:                  Bomber
+nocreate
$Turrets prioritize ship target: NO

#End

Fixed.

[Fury]

Figured +nocreate would work.

Anyhow, is there a reason why 3.6.11 debug build has significantly lower framerates than 3.6.10 debug builds? I cannot say anything about 3.6.11 retail-build, because it doesn't load up missions most of the time, so I've been stuck using debug. By average it seems like 3.6.11 has about half the framerate of 3.6.10.

[portej05]

In a debug build, the Assertion code remain in the codebase - most functions have at least one
vm_malloc uses the SCP allocator (not the template one, the one in windebug.cpp) in debug builds
Visual Studio inserts all sorts of debugging junk (to quote sandsmark: 'Canaries') into the code.

It's no real surprise that debug is a lot slower.

[Fury]

I was comparing 3.6.10 debug to 3.6.11 debug. .10 has about double the framerate compared to .11.

[portej05]

I was comparing 3.6.10 debug to 3.6.11 debug. .10 has about double the framerate compared to .11.

hmm... time to break out the profilers again.

[chief1983]

Fury, go back a couple weeks and see if the problem still exists in the nightlies there, everyone else has been reporting massive speed improvements with 3.6.11.  You're the first report of a slowdown I'm aware of.

[Fury]

Can someone provide me a debug build with pdb+map that has $Arm radius assert fix? I have another assert I need to track down. Thanks.

[Flaser]

Get rid of them, They're part of the code and don't need to be in the actual table.

Unless the modder works on something like a gunship class IIRC. Then object types becomes a very important table.

[Wanderer]

Get rid of them, They're part of the code and don't need to be in the actual table.

Unless the modder works on something like a gunship class IIRC. Then object types becomes a very important table.

Well, first of all the characters mentioned do not need to  be in any table that has been extracted from the code. Second thing, it is not adviseable to use objecttypes.tbl to create new ship types. Editing of the existing retail types is ok, but creation of new entries is certainly not. That is you can create them but unless you (what was the term coined with it...) 'multiclass' the ship type with some existing ship class (not 100% sure how this would work out and how it is done) then you may encounter very unexpected behaviour.

[portej05]

I put the attached patch together for The_E.
Symptoms include NULL dereferencing if Cutscenes of Cutscene_list is 0 sized.
I don't know what knock-on effects this may have.
I suspect the if (str) may have been for this very case before it used vectors.

[attachment deleted by Tolwyn]

[The E]

To elaborate: This caused a crash on TBP, that could be tracked down to having an "empty" cutscenes.tbl (With nothing but #Cutscenes and #end in it). BTW, with that patch, while the game doesn't crash, it doesn't put out a warning or assertion either.

[portej05]

To elaborate: This caused a crash on TBP, that could be tracked down to having an "empty" cutscenes.tbl (With nothing but #Cutscenes and #end in it). BTW, with that patch, while the game doesn't crash, it doesn't put out a warning or assertion either.

It's not actually warning or error worthy material.
The code there as it is was checking to see whether there was something in the array (by using str == NULL), it has been converted to use SCP_vector.
This is why we have to be careful when we change to the vector, as it doesn't like being dereferenced it it's empty!

[The E]

Upon reflection, I can see that and agree. It's more of a case of :V: not planning for having no cutscenes.

[Spicious]

• Turret targeting priorities setup
  

Does this work on a ship granularity?

[Angelus]

Instead of creating a new thread, i'll post in here since it's related to the new 3.6.11 features.
This is not a "bug report", rather a question regarding the new feats.

The Nightly build 5502 crashed right on start, i didn't know why, since i didn't change anything in the folder.
The first error message of the debug build revealed the error, a "rogue" texture in the maps folder i forgot to delete months ago.

I wonder why the engine complains about a map that's not used by any model?


Anyway, the new features are really cool AND useful and they help me to keep my folder clean.

[chief1983]

It's likely the texture had a filename that was too long.  The entire filesystem for all loaded mods is scanned, so that it doesn't have to scan it again later when looking for textures, etc.  That means any filename too long for the filename buffer used to be capable of corrupting memory.  That's now been fixed, but any filename that long will cause an assertion.  It should help stabilize the engine overall once people clean up their mods of long filenames.

[Wanderer]

• Turret targeting priorities setup
  

Does this work on a ship granularity?

Specific ship level? Nope, it wont... mainly because its still only a table controlled feature and at table parsing phase there are no ships yet (only ship classes). Besides that should be possible to handle with fredding means.

Options are ATM limited to - all with inclusive or so using say object type ship as targeting criteria automatically allows targeting of all ships regardless of any further checks - following list... (only certain flags are allowed... check wiki)

• Object type
• Weapon Class
• Object Flags
• Ship Class Flags
• Weapon Class Flags
• Ship Type (in objecttypes.tbl)
• Ship Class (in ships.tbl)

[Angelus]

It's likely the texture had a filename that was too long.  The entire filesystem for all loaded mods is scanned, so that it doesn't have to scan it again later when looking for textures, etc.  That means any filename too long for the filename buffer used to be capable of corrupting memory.  That's now been fixed, but any filename that long will cause an assertion.  It should help stabilize the engine overall once people clean up their mods of long filenames.

Thx, for clarification, the filename of the unused map was "Deletethisragnar-shine" without the quotes.

[Fury]

That can't be too long for a filename. Or are we stuck with 3+8 here?