© 2003-2025 Ironclad Games Corporation Vancouver, BC. All rights reserved.
© 2006-2025 Stardock Entertainment
Search
Forum Home | Login
We have re-enabled logins for the forums, please be aware that you may need to reset your password or register for an account again while we continue to restore full functionality.
SZ0
SZ0
Join Date 05/2008
+38

Pesky error, can't find cause.

c:\projects\Perforce\SinsDiplomacy\main\CodeSource\GS\Entity\Interfaces\IAbility.cpp(1663): assert! [false]

September 11, 2010 10:45:21 PM from Sins of a Solar Empire ForumsSins of a Solar Empire Forums

Has any body come across this dev. exe error before.

c:\projects\Perforce\SinsDiplomacy\main\CodeSource\GS\Entity\Interfaces\IAbility.cpp(1663): assert! [false]

It persistently pops up in game when running the Dev. exe

Using normal diplomacy everything seems fine for quite awhile but then crash's unexpectedly.

Is it referring to an ability? if so what does the (1663) indicate. I'm pretty sure there aren't that many abilities.

modding
Locked Post
Search this post
Advanced Search
Subscription Options
Reason for Karma (Optional)
Successfully updated karma reason!
SZ0
myfist0
Join Date 01/2010
+319
Reply #1 September 11, 2010 10:49:55 PM
from Sins of a Solar Empire ForumsSins of a Solar Empire Forums

How many new abilities did you add? If not that many remove and slowly put back. I have had that but quickly removed from sins plus or celestial boobies abilities are all removed so far in mine.

Crashing later tells me that its a later game ability that when you or the AI gets it, it goes boom.

Reason for Karma (Optional)
Successfully updated karma reason!
SZ0
SZ0
Join Date 05/2008
+38
Reply #2 September 11, 2010 11:44:31 PM
from Sins of a Solar Empire ForumsSins of a Solar Empire Forums

There are 7 new abilities. I have tried removing those abilities 1 at a time at from the ship that seems to be causing the problem, perhaps it is 1 of the others that the AI may be using. The error does appears before any ships have been made straight after loading regularly also, which is baffling. The odd thing is this only started happening after changing all the targa files to dds. Perhaps it is an ability brush reference or something.

Reason for Karma (Optional)
Successfully updated karma reason!
SZ0
myfist0
Join Date 01/2010
+319
Reply #3 September 12, 2010 12:10:05 AM
from Sins of a Solar Empire ForumsSins of a Solar Empire Forums

Unless its a new brush it will just look to the default files and I have had specific "Missing Brush" errors.

Make sure the brushes texture links all have the .dds extention.

Reason for Karma (Optional)
Successfully updated karma reason!
SZ0
SZ0
Join Date 05/2008
+38
Reply #4 September 12, 2010 1:22:26 AM
from Sins of a Solar Empire ForumsSins of a Solar Empire Forums

The crashing happens every time a particular ship enters the gravity well of a star, not always straight away but at some time its there.

Reason for Karma (Optional)
Successfully updated karma reason!
SZ0
Major Stress
Join Date 05/2006
+161
Reply #5 September 12, 2010 11:12:31 AM
from Sins of a Solar Empire ForumsSins of a Solar Empire Forums

I get that error too on VANILLA Sins running dev exe. Get it all of the time with TSOP. TSOP added or changed nothing stat wise. So it must be a vanilla bug.

Reason for Karma (Optional)
Successfully updated karma reason!
SZ0
SZ0
Join Date 05/2008
+38
Reply #6 September 15, 2010 6:47:28 AM
from Sins of a Solar Empire ForumsSins of a Solar Empire Forums

I think I may have found the cause. Unless its just a big coincidence. Could you please try restoring the "Unit_Infocard" back to Targa to confirm this.

Edit ; Nah don't worry, Dopey me saved them as DXT NM instead of RGBA. OOPS!

Reason for Karma (Optional)
Successfully updated karma reason!
SZ0
SZ0
Join Date 05/2008
+38
Reply #7 September 16, 2010 6:14:06 AM
from Sins of a Solar Empire ForumsSins of a Solar Empire Forums

Well it must have been a coincidence. After running the game for some time no crash, no error. Now both have returned.

In the debug file I get this

c:\projects\Perforce\SinsDiplomacy\main\CodeSource\Engine\DataStructures\DynamicArray.h(128): assert! [i < size]
c:\projects\Perforce\SinsDiplomacy\main\CodeSource\Engine\DataStructures\DynamicArray.h(128): assert! [i < size]
c:\projects\Perforce\SinsDiplomacy\main\CodeSource\Engine\DataStructures\DynamicArray.h(128): assert! [i < size]
c:\projects\Perforce\SinsDiplomacy\main\CodeSource\Engine\DataStructures\DynamicArray.h(128): assert! [i < size]
c:\projects\Perforce\SinsDiplomacy\main\CodeSource\Engine\DataStructures\DynamicArray.h(128): assert! [i < size]
c:\projects\Perforce\SinsDiplomacy\main\CodeSource\Engine\DataStructures\DynamicVector.h(183): assert! [i < m_CurrentSize]
c:\projects\Perforce\SinsDiplomacy\main\CodeSource\Engine\DataStructures\DynamicVector.h(183): assert! [i < m_CurrentSize]
c:\projects\Perforce\SinsDiplomacy\main\CodeSource\Engine\DataStructures\DynamicVector.h(183): assert! [i < m_CurrentSize]
c:\projects\Perforce\SinsDiplomacy\main\CodeSource\Engine\DataStructures\DynamicVector.h(183): assert! [i < m_CurrentSize]

Has anyone ever tried to use texture files of varying sizes for 1 mesh? my normal maps are twice the size of the cl, da, I wonder if this may be the cause???

Edit:Nope that's not it

Reason for Karma (Optional)
Successfully updated karma reason!
View all recent posts
Mark all posts as read Delete cookies created by the forum Return to Top
Stardock Forums v        Server Load Time:   Page Render Time: