Jerome, "still existing VERTEX_BUFFER error"?

[lt1956]

Jerome, Myself and few others are getting these Errors with some of our skins or models. I have no idea what these errors mean, but since I am not the only one getting them now I thought I would post to ask. It is a wierd error that seems to happen only with 1.3 or BI, our models and skins had no such error in 1.2

Anyway, if you could shed some light on this thanks. So far we all making progress on all the issues, just a very slow pace.

Thanks for your time.

lt1956

P.S. Dont forget to read the -mod thread, I had some ideas to fix the naming legions.

There were 8 un-destroyed logged items:

still existing VERTEX_BUFFER 0x10508CF8 creation: 1133
still existing VERTEX_BUFFER 0x10477DE8 creation: 1130
still existing VERTEX_BUFFER 0x10452EC8 creation: 1138
still existing VERTEX_BUFFER 0x104F6950 creation: 1139
still existing VERTEX_BUFFER 0x104C33B0 creation: 1132
still existing VERTEX_BUFFER 0x10524D40 creation: 1141
still existing VERTEX_BUFFER 0x10532090 creation: 1136
still existing VERTEX_BUFFER 0x1052BCE0 creation: 1135

add cmd_line option break_vertex_buffer=999 to break in the 999th creation
add cmd_line option break_index_buffer=999 to break in the 999th creation
add cmd_line option break_texture=999 to break in the 999th creation
add cmd_line option break_surface=999 to break in the 999th creation

[Centurion Cato]

I've also encountered this error message when adding ferres models & skins. However after rechecking the DMB file i found that i'd made a mistake with my new entry. I fixed the error in the DMB and the vertex issue was resolved. I doubt this will help you, but that was how i resovled the issue.

Maybe if you post the DMB & EDU entries and the actual files i could see if i could replicate the error...BTW is it a legion unit your trying to add?

[lt1956]

Well mine where in a Working DMB for 1.2 and only now do that in RTW 1.3 I have added a couple units so far Using the 1.3 DMB, But that means I have to add all in one line at a time and really the 1.2 should port right over, there seems to be some issues with 1.2 stuff not working in 1.3 and its a little excessive really. I can see the descr_start file etc, but our DMB and units file shouldnt especially when there are no syntax errors mentioned.

I just dont feel 1.3 is worth the effort to port over, BI MIGHT be IF some issues are resolved. Namely the -mod switch, Pilum AI firing, 1st cohort naming, Maps to work without having to use some fan made converter, not everyone uses the Java program he recommends, better 1.2 compatibility. I guess thats it really for me, but its enough to stop me from even working on it. Right now I removed BI to save room for other work, but if a patch resolves the issues without creating new serious ones, then I have no problem starting over to utilize the new features.

Lt

P.S. No it was a custom SPQR unit, but I had the crashes with the Roman units also most are ferres models and skins. My DMB is totally useless in 1.3 or BI, the amount of extra work for NO reason is what is turning me off with BI, I mean I have a very fun and enjoyable mod on 1.2 that has very little issues. But BI is better for a Republic mod. And that was my next project after SPQR, but with all these issues, I dont know. I really dont like the way the added the legion naming, and pilum bug is serious IMO, but more important is the -mod, I dont like overwriting the stock files with BI especially the WAYits done since its an addon in itself. I tinkered, and see I will have to recreate the map from scratch, but I prefer to port as much as possible to BI from 1.2 and it seems we cant unless by hand. I alreadt had my republic map made since several months ago, but now its useless, because of it not working in BI.

[Centurion Cato]

Well so far B.I has been a good experience for me. I've been able to port over a lot the FRRE content, that includes our map and units, even custom (modified) skins i've made with great success. B.I has far to much value for the FRRE project that i can't see us reverting to 1.2 unless we come across a serious problem. I suppose the major niggle at the moment is the -mod switch capability, but it's not a showstopper IMO. We plan to have legion system that was tested in 1.2 and should work just as well in B.I. I guess we always expected that B.I would be a lot of work to port over to, but progress is going well and community as always are working hard to find out how B.I works.

[Lord Adherbal]

whenever I encountered this error it was followed by a warning that the lowest LOD distance value was not set to "max". Fixing those mistakes solved all the problems for me.

[lt1956]

I've gotten some weird errors on my DMB file. Like a missing cas file which wasnt from my mod. lol So I figure if I redo all the entries by hand it should work as I added a model with no problem "IF" I did so using the 1.3 DMB file.

I am hoping Cata that CA will fix the Legion numbering system to have it track ALL the 1st cohorts for the player and number them consecutively. Otherwise Like you I will Port over SPQRs naming convention, but I STILL think it would have been neat to have province based naming.

So you got the Cmapign map from TFT to work in BI? Anything edited in paticular? Reason I asked is my map doesnt seem to work or is it that hgt file or what have you?

Lt