[http://sourceforge.net/p/ufoai/bugs/2482 Item 2482] imported from sourceforge.net tracker on 2013-01-28 19:35:59

Base - Buy\Sell screeen - 'Other' tab
when clicking have assertion failed.
System: Windows 7 x64, geForce gtx295
Game settings: 1680x1050, all in highes lvl

Started campaign using russian language when got error switched to english - still have assertion failed
===== Comments Ported from Sourceforge =====

====== estarioll (2010-05-04 23:17:00) ======


====== estarioll (2010-05-04 23:17:58) ======

Also got this error when clicked some button in sam site popup menu
====== tlh2000 (2010-05-05 06:20:28) ======

the assert is fixed in r29761 - but there is still an error left in loading the model data. the samlauncher model should only have ~1000 verts - but the warning that the model has more and 4096 verts is still printed (the num_verts is loaded from the mdx file - we need more sanity checks there, too). left open until this issue is discussed
====== tlh2000 (2010-05-05 06:34:50) ======

one problem might be that if we update the model and the user already has the mdx file calculated, this might break things heavily. we have to ensure that the number of indices and verts from the mdx file match the number of indices (tris * 3) and verts from the model file
====== arisian (2010-05-05 13:52:35) ======

The whole MDX format is still a work-in-progress; there are a lot of efficiency issues. But one thing to consider is that the number of verticies in the MDX is likely to be much higher than the number of verticies in the MD2 file. This is because the MDX file often needs multiple "vertex" objects that map to the same location, but have different normal/tangent/texcoord values. I think it may be splitting more verticies than it should really have to, as well, but I'm not sure if this is the case (or if so, why).
====== arisian (2010-05-09 00:39:03) ======

I think this should be fixed now; let me know if anyone is still having issues with this.
====== sf-robot (2010-05-23 02:20:15) ======

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).