Hard Light Productions Forums
Off-Topic Discussion => General Discussion => Topic started by: The Refugee on August 18, 2002, 10:53:11 pm
-
I recently made a fighter from FS2 and put it into the main FS1 directory. When i ran a mission i made to test it and some weapons that i had working quite well, it got to 1 bar on the loading screen kicked me out and said "Can't find file mx-50.pof
C:\desktop\freespace\model\modelread.cfg or somethin like this does any one know how to correct this so i can fly the Hercules MkII in FS1:confused: Please post back A.S.A.P I would greatly appreciate any info you have to shed some light on the problem
Thanks ahead of time the Refugee
-
Its simple... it cant find MX-50.pof... You have, in the weapons table, a weapon that has MX-50.pof as the model file, and Freespace cannot find that model within its reachable resources (freespace.vp, /data/models)
-
Just reinstall the game to make sure all the vp's are intact. And welcome to the board.
-
i have rinstalled it slent threat and the 1.06 patch a total of 42 times already. shadowwolf_ih said to go into a pof editor or somethin and rebuild herc mk2 for fs1 but i dont know how to do that. and if you can i would like to know how to make my own ships. i put the mx-50.pof file in the main fs1 directory and it still did that:mad: hwat the f*** is up with that:confused: :confused:
-
Originally posted by The Refugee
i put the mx-50.pof file in the main fs1 directory and it still did that:mad: hwat the f*** is up with that:confused: :confused:
I thought you said it was the MX-50.pof, case makes a very large difference. Also try putting it into /data/models
-
A freespace2 model doesn't work in FS1 whitout converting it to FS1 .pof format. Also copying the herc2's TBL entry doesn't work as FS1 doesn't suport neb trails and some other flags.
-
how do i put into data\models and this is the error i get it goes back and forth bewtween mx50 and hornet tat i know of..
Error: Can't open file
File:C:\Windows\Desktop\FSv106\fsv106\Model\ModelRead.cpp
Line: 989
Call stack:
------------------------------------------------------------------
------------------------------------------------------------------
this is the exact error i get when i try to fly the herc mk2 i made in fs1
-
i told him to first get the mission manager so that he could change the pof to fs1. it will build it on it's own that way.
-
i got that modelview32 or whatever i channged the hercs file to fs1 i did that without a prob. i put all the texture(again) into the data\models file were i saved the herc2 fs1 pof. i got all the interface and hud stuff put it all in the data\model directory. I copied the tbl file and inputed it into the fs1 tbl right under the origional herc. i took out the contrail stuff and the shield color made the same exact lines as the herc for my herc2 exept i put in the tech desrip from fs2. when i ran fred to put the herc2 into a mission upun booting up fred i got this:
Error: Error parsing 'ships.tbl'
Error code = 4.
File:D:\PROJECTS\FREESPACE\Ship\Ship.cpp
Line: 923
Call stack:
------------------------------------------------------------------
FRED.EXE 004017e2()
FRED.EXE 0042568c()
FRED.EXE 00425589()
FRED.EXE 00581f6a()
FRED.EXE 00595a31()
FRED.EXE 00595ab0()
FRED.EXE 0057f5e2()
FRED.EXE 0057f26d()
FRED.EXE 0057e01e()
FRED.EXE 0057e32a()
KERNEL32.DLL bff7363b()
KERNEL32.DLL bff94407()
------------------------------------------------------------------
should i just copy the hercules tbl file and modify the pof file etc. to use the herc2 stuff would that work. i just really want to fly the herc2 in fs1
-
textures go in maps......
copying the fs2 table entry will not help....they aren't compatible.
copying the herc entry fs1, pasting the herc entry fs1, renaming the herc entry herc2 will solve that. Then just go thorugh it line by line and replace THE PERTINENT INFO in the fs1 table with what it says in the fs 2 table. you can't add all of the stuff from fs2 table. but speed, manouverability, etc etc....basically anything in the fs1 table can be found in the fs2 table. just use those stats.
also find out which icon si used for herc 2, which loadout, which shield icon.
put icon and loadout in a folder called interface......
put shield icon in a folder called hud........
and edit the hud table to reflect the new shield icon.
here's a hint......
all pof's go in models
all textures go in maps
fs1 and 2 have the same file system, with minor variation, however the two are not compatible.
-
ok so the copying herc1 was a good idea but what do you mean pernitnet info??? and im not going to do fs2 stats for herc 2 i want to have the herc2 in fs1 so i can finally build my Timmachine campain what happens is an apollo's subspace drive malfunctions goes haywire and he goes 300 yrs into the future and manages to steal som herc2 plans the herc 2 will have a MAIN speed of around 550 and its olck speed will be 700 and aftrbrn will be around 1300.!!! whitch tranlates into "The Shivans are F***ed!"
-
Use punctuation, and use FS2. You can have the Herc I and II in there, and if you download the Port you can have all the other FS1 ships too.
-
the port p1mpmaster, at your service, lol...
-
Originally posted by GalacticEmperor
Use punctuation, and use FS2. You can have the Herc I and II in there, and if you download the Port you can have all the other FS1 ships too.
You should add that to your sig.
*Looks at sig*
Oh. :p
-
Actually I've found that FS2 will use models in the game directory before it will look for them in the data/models folder. Try working on a model with an older copy saved in the main directory; the changes you make to the one in the data/models folder don't apply even though they are saved. The search pattern for refrenced models is:
FS2 Main > FS2 Main/Data/Models > Custom VP files > original VP files
and I suspect the same is true for any file type. Having the data directory and subdirectories makes it cleaner, that's all. Also a good way of installing a distribution mod without chance overwriting any existing files, though it only will work once before files have to be overwritten anyway.