Hard Light Productions Forums
Modding, Mission Design, and Coding => The Modding Workshop => Topic started by: CaptainX on December 02, 2007, 08:06:01 pm
-
Greetings everyone.
After searching these forums high and low, I cannot seem to find the solution to this particular error:
Error: Can't open model file <none>
File:J:\src\cvs\fs2_open_3_6_9.final\code\Model\ModelRead.cpp
Line: 1899
[This filename points to the location of a file on the computer that built this executable]
Call stack:
------------------------------------------------------------------
------------------------------------------------------------------
I have seen that other people have had problems with this, but none of the posts ever offered an answer... a couple of times the OP just replied and said he fixed it (with no explanation how), and a couple other posts just plain died.
This particular error is actually coming up on the WC: Saga installation with a few mods, but it uses the same file structure as FS2, so I thought I'd find out how you guys solved this error.
This error seems to be originating from the "Additional-09-26-07" VP file supplied by Scooby Doo for his Big Mod Release of WC ships. I believe the problem lies within a weapons table within this file, but I have no idea how to fix it.
Any ideas?
-
Let me take a look.
What exactly where you doing when this happened?
-
Alrighty. I'll be standing by... if you have any IM programs, let me know and we can chat in real time.
The Additional VP file originally gave an error about not finding torp.pof, the model for the Cruise Missile... after changing that to Torpedo.pof, it moved on to the "none" error.
I was attempting to run a mission when the error occurred. Also, I updated the Saga.exe with the newest exe from SCP, now the error is coming up on Line 1902, instead of 1899.
-
Try extracting the saga-confed-wep.tbm from the vp.
in the very last entry Cruise Missile change
$Model File: torp.pof ;Torpedo.pof
to
$Model File: Torpedo.pof
oh wait... you already fixed that...
How about renaming Cruise Missile to something else, I just noticed theres a Cruise Missile in sagas data table
-
:lol: Yup, I'm one step ahead of ya.
I dunno why it's looking for a "none" model file... the only things I see in the table that have "none" are all of the guns. That's why the whole thing baffles me.
-
Tried renaming the cruise missille? Also what ships were you trying to use, I could see if I could recreate the scenario and hopefully get that error message too
-
I'm using the Midway, the Korvak, The Pirahna fighter, and the Dralthi fighter.
I can email you a copy of the mission if you'd like.
-
Whats the Korvak? BTW the midway suffers from lack of collision detection.
Also what build are you using? (or at least a link to it)
hmmm still not getting that error.
Send an email here: skaarjy @ Yahoo [dot] com
-
I mean the Kavor... LOL, my bad :p
Mission sent via email.
I am currently using the fs2_open_3_6_9 build, the most recent version released by SCP (I think LOL).
I should also point out that I did not download every single ship from your big mod release... are there any of those ships that include vital files?
-
Hmmm strange still produces no error, although I should really retweak the laser turret refire rate. :shaking:
The only vital files are in the additional package.
Hmmm try copying and pasting here the debug spew.
-
Here's what comes up when I run the FRED2 debug:
Warning: Unable to find WEAPON_LIST_TYPE string "Heavy Pulse Beam"
in ship: @Aurora's default primary banks.
File:J:\src\cvs\fs2_open_3_6_9.final\code\Parse\PARSELO.CPP
Line: 2451
[This filename points to the location of a file on the computer that built this executable]
Call stack:
------------------------------------------------------------------
fred2_open_3_6_9_debug.exe 0052adf5()
fred2_open_3_6_9_debug.exe 0052c5a2()
fred2_open_3_6_9_debug.exe 00510758()
fred2_open_3_6_9_debug.exe 0052ca87()
fred2_open_3_6_9_debug.exe 00455bbf()
fred2_open_3_6_9_debug.exe 0044c951()
fred2_open_3_6_9_debug.exe 009ba792()
fred2_open_3_6_9_debug.exe 009ba0f4()
fred2_open_3_6_9_debug.exe 009b7c49()
fred2_open_3_6_9_debug.exe 009b8135()
USER32.dll 7e418734()
USER32.dll 7e41d05b()
USER32.dll 7e41b4c0()
USER32.dll 7e41f9fe()
ntdll.dll 7c90eae3()
------------------------------------------------------------------
Warning: Unable to find WEAPON_LIST_TYPE string "Heavy Pulse Beam"
in ship: @Aurora's default primary banks.
File:J:\src\cvs\fs2_open_3_6_9.final\code\Parse\PARSELO.CPP
Line: 2451
[This filename points to the location of a file on the computer that built this executable]
Call stack:
------------------------------------------------------------------
fred2_open_3_6_9_debug.exe 0052adf5()
fred2_open_3_6_9_debug.exe 0052c5a2()
fred2_open_3_6_9_debug.exe 00510758()
fred2_open_3_6_9_debug.exe 0052ca87()
fred2_open_3_6_9_debug.exe 00455bbf()
fred2_open_3_6_9_debug.exe 0044c951()
fred2_open_3_6_9_debug.exe 009ba792()
fred2_open_3_6_9_debug.exe 009ba0f4()
fred2_open_3_6_9_debug.exe 009b7c49()
fred2_open_3_6_9_debug.exe 009b8135()
USER32.dll 7e418734()
USER32.dll 7e41d05b()
USER32.dll 7e41b4c0()
USER32.dll 7e41f9fe()
ntdll.dll 7c90eae3()
------------------------------------------------------------------
Warning: Unable to find WEAPON_LIST_TYPE string "Small Antimatter"
in ship: Kavor's default primary banks.
File:J:\src\cvs\fs2_open_3_6_9.final\code\Parse\PARSELO.CPP
Line: 2451
[This filename points to the location of a file on the computer that built this executable]
Call stack:
------------------------------------------------------------------
fred2_open_3_6_9_debug.exe 0052adf5()
fred2_open_3_6_9_debug.exe 0052c5a2()
fred2_open_3_6_9_debug.exe 00510758()
fred2_open_3_6_9_debug.exe 0052ca87()
fred2_open_3_6_9_debug.exe 00455bbf()
fred2_open_3_6_9_debug.exe 0044c951()
fred2_open_3_6_9_debug.exe 009ba792()
fred2_open_3_6_9_debug.exe 009ba0f4()
fred2_open_3_6_9_debug.exe 009b7c49()
fred2_open_3_6_9_debug.exe 009b8135()
USER32.dll 7e418734()
USER32.dll 7e41d05b()
USER32.dll 7e41b4c0()
USER32.dll 7e41f9fe()
ntdll.dll 7c90eae3()
------------------------------------------------------------------
Warning: Unable to find WEAPON_LIST_TYPE string "Small Antimatter"
in ship: Kavor's default primary banks.
File:J:\src\cvs\fs2_open_3_6_9.final\code\Parse\PARSELO.CPP
Line: 2451
[This filename points to the location of a file on the computer that built this executable]
Call stack:
------------------------------------------------------------------
fred2_open_3_6_9_debug.exe 0052adf5()
fred2_open_3_6_9_debug.exe 0052c5a2()
fred2_open_3_6_9_debug.exe 00510758()
fred2_open_3_6_9_debug.exe 0052ca87()
fred2_open_3_6_9_debug.exe 00455bbf()
fred2_open_3_6_9_debug.exe 0044c951()
fred2_open_3_6_9_debug.exe 009ba792()
fred2_open_3_6_9_debug.exe 009ba0f4()
fred2_open_3_6_9_debug.exe 009b7c49()
fred2_open_3_6_9_debug.exe 009b8135()
USER32.dll 7e418734()
USER32.dll 7e41d05b()
USER32.dll 7e41b4c0()
USER32.dll 7e41f9fe()
ntdll.dll 7c90eae3()
------------------------------------------------------------------
-
Give me a couple minutes and I'll fix those two sets of errors, maybe thats whats causing it :confused:
-
It's quite strange that you're not getting any errors... here is the step by step process of what I did:
1. I downloaded and installed the WC Saga package.
2. I updated the Saga exe to the current 3.6.9 build of SCP.
3. I downloaded a bunch of your modded ships, all from your Big Mod Release.
4. I placed the VP files into the data directory as they are.
5. I fixed the torp.pof error in the weapons file.
6. I made the mission and attempted to run it.
That's it... maybe I messed something up somewhere :shaking:
-
Try using this for Saga-confed-wep.tbm in the attachment.
Note I'll have to go through the other cap ships and see if they need weapon names updated too. Not sure how those two misnamed got past me.
[attachment deleted by admin]
-
Nope, no luck on that one either.
However, I do have one piece of useful info. I removed ALL of the ships of yours that I installed, and left ONLY the Additional VP file and the confed weapons table in their locations.
Doing this still gives the error.
Removing the Additional VP file and the confed weapons table does NOT produce the error.
So we can pretty much assume that the error is somewhere in that VP or the weapons table.
-
Ugh I need to clean up my weapons table, my naming convention sucks badly.
Hmmm try taking everything out except for the saga-confed-wep.tbm
-
Hmm... interesting.
I took out everything except the weapons table. It gave me an error about the mass.pof, so I extracted that and threw it into the models directory.
And viola... no model error!
So the error can't be in the weapons table... can it be somewhere else in the Additional VP?
***Edit*** The neph weapons table... I don't use any Neph ships at all... can this be the issue?
-
try adding the neph-wep.tbm and see if complains then.
if your not using neph weapons, then delete it.... honestly I don't know if i'm going to be expanding on this anyways.
-
Another interesting piece of info.
I did the same thing I did before... I removed everything except the Additional VP and the confed weps table. Now the damn thing works with no error.
So it might not be in the additional VP after all... I'm gonna add the ships back one at a time and see which one causes the error again.
I'll post back here in a few.
-
Are you using any one of these ships: Ajax, Athena, Formidable, HHaifra, Hunter, Nimitz or the Rak? If so I'll have to send you updated versions, fixed the naming conventions (I had small plasma, medium plasma, heavy plasma, light antimatter, medium antimatter, large antimatter, everythings now light, medium heavy).
-
Okay, now I'm completely confused.
I created a new mission in FRED and added the same 4 ships that were used in my other mission. This new mission works fined with no errors.
The old mission, however, still fails with the model error.
On the bright side, the error seems to be fixed, except for the problem of my other mission (which took hours to create) still won't work. But the error must not lie in the VP file as originally thought, otherwise this new mission would throw up an error too, right?
Well... back to the drawing board I suppose. I hate unsolved problems.
P.S. Yes, I am using the Ajax, Formidable, HHaifra, and Nimitz.
-
New error info.
I ran the debugger on my specific mission. This is what happens:
Warning: Invalid subobj_num or model_num in subsystem 'engine04' on ship type 'Kavor'.
Not linking into ship!
(This warning means that a subsystem was present in vampire-shp.tbm and not present in the model
it should probably be removed from the table or added to the model.)
File:J:\src\cvs\fs2_open_3_6_9.final\code\ship\Ship.cpp
Line: 5690
[This filename points to the location of a file on the computer that built this executable]
Call stack:
------------------------------------------------------------------
fred2_open_3_6_9_debug.exe 0052df38()
fred2_open_3_6_9_debug.exe 005366bc()
fred2_open_3_6_9_debug.exe 004ee3bf()
fred2_open_3_6_9_debug.exe 004ee297()
fred2_open_3_6_9_debug.exe 004f14f6()
fred2_open_3_6_9_debug.exe 004f3ad4()
fred2_open_3_6_9_debug.exe 004f5767()
fred2_open_3_6_9_debug.exe 004f5726()
fred2_open_3_6_9_debug.exe 004f65a8()
fred2_open_3_6_9_debug.exe 00433424()
fred2_open_3_6_9_debug.exe 00432908()
fred2_open_3_6_9_debug.exe 009d6e16()
fred2_open_3_6_9_debug.exe 009dd0b5()
fred2_open_3_6_9_debug.exe 009e9095()
fred2_open_3_6_9_debug.exe 009f53b9()
------------------------------------------------------------------
The funny thing is that the tbm referenced above (in this case the vampire tbm) will be replaced by whatever tbm is last on the list alphabetically if I delete the vampire tbm. This error happens 4 times, on all 4 engines of the Kavor.
I'm not sure what this means, but maybe it can be useful...?
-
I'm uploading some fixes, it'll be a little while (upload is slow)
As for it saying about the vampire, i think thats been messed up for ages, since the warning is concerning about Kavor and not the vampire.
As for that warning, I'm not sure exactly what's going on there. The table has four engine entries and the model has four engine special points and 4 thrusters :confused: Personally, I'd ignore it for the time being.
When I get my new video card I'm going to go over all the ships give them normal maps and hopefully clear up any issues like this.
-
I've pretty much confirmed that whatever this problem is, it HAS to be this specific mission file. I'm not getting the error anymore when I create anything new.
I just wish I knew of a way to save this mission... the events took forever to script.
***Edit*** Now ALL the missions are throwing up the error again... damn, I give up.
-
I've pretty much confirmed that whatever this problem is, it HAS to be this specific mission file. I'm not getting the error anymore when I create anything new.
I just wish I knew of a way to save this mission... the events took forever to script.
Ugh that sucks... I really liked your autolaunch :yes: (wish there was an easy way to boosted launch of fighter like in Prophecy) Also is it just me or are the missiles overly deadly? The strange thing is their stats are identical to those of saga, and I can chew through saga ships without taking much damage, but when attacked by my missiles YOUCH.
LOL I nominate you as my debugger :P
-
I have no idea where the problem is, since now every mission throws up the model error.
I have discovered that I can break into the debugger and continue the mission. I've also discovered that if I try to select my ship's weapons, it throws up a WHOLE BUNCH of "none" model errors.
Should the guns that are listed in the confed weapons table have models?
-
Is this occuring with weapons like lasers? (stuff that comes with saga)
-
I have no idea, it doesn't give any details as to which weapons are causing the errors. As soon as I go to the weapons screen, it throws up tons of them.
I guess I uninstall Saga completely and reinstall it... for the second time today. Maybe that will fix it.
I'll have to worry about that tomorrow, though. I gotta get some sleep... gotta be at work in 7 hours.
I'll post here when I have more info. Let me know if you release any updated versions of your files.
-
Have a good night, taking some time off might give a new idea whats causing the problem.
I've already updated stuff, http://www.hard-light.net/forums/index.php/topic,45276.msg1025382.html#msg1025382 (http://www.hard-light.net/forums/index.php/topic,45276.msg1025382.html#msg1025382)
Worst case scenario, remove my mod, and test with just saga stuff.
-
I got that error several times. It's irritating to say the least and I found 3 ways to get rid of it:
- table change (usually some redicolous, uninportant trinket)
- exe change
- new mission
-
Do you have 3D ship selection on ? mv_core.vp fixed this problem to me when Blue Planet done that . Dunno about WCS .
-
Okay new update.
I completely uninstalled WC Saga and all mods.
I then reinstalled Saga and all mods. The old mission throws up the model error, and any new ones created do also.
I am completely at a loss on how to fix this problem. If someone wants me to send them the weapons table file that I believe is causing this error, send me with your email and I'll send it to you. Maybe someone else can find the problem.
Until then, I'll just have to keep hitting OK on the error message. That at least lets me back into the game. It really lowers the mission quality, but they are still playable.
-
If anyone thinks this might help, the model error comes up exactly twice each time I start a mission.
Could mean that there are two entries somewhere where there should actually be a model file... I dunno.
-
Try using this build and see if it occurs: http://icculus.org/~taylor/fso/willrobinson/Xt1126-win32.rar (http://icculus.org/~taylor/fso/willrobinson/Xt1126-win32.rar)
-
That particular build does NOT cause the model error on any of the missions... so what does that mean? LOL.
-
Your cursed :lol: Honestly i don't know, i've been using taylors builds since he is doing stuff for saga.
-
Can you, by chance, give me a run down on what is different in this build than in the original SCP build? I'm thinking of replacing my original FS2 install with this one as well, after seeing the new options in FRED.
Well, at least all the errors are gone... and I like this build better anyways :lol:
-
You'll have to ask taylor, although some stuff is probably private for saga.
-
Hello. I am in fact one of those people who fixed it by myself with no explanation :p
My problem was that I changed the primary graphic to a pcx when I was customizing a weapon. It kept looking for a model called <none> for a long time, severely pissed me off and then I simply converted the graphic to a dds. Problem solved. Weird. Hope this helps! :D
-
You know what... I bet that could be it, theres two or three pcx files in the effects folder. I couldn't convert them to dds and keep their transparency.
-
LOL Sounds like you found the error :)
That's okay though, the other build you gave me works splendidly, and has some NICE options in FRED.