ONaN's 2.1 FiTruck2.pod (28in1)
- SkeletonKing
- Diggerdude
- Posts: 176
- Joined: Sun May 13, 2007 11:32 am
- Location: Behind You
- Contact:
ONaN's 2.1 FiTruck2.pod (28in1)
Im assuming its a remake of all the stocks in the game but when i pod it the game wont start, i opend the pod up in binedit and there nice looking too anyone else have this problem?

- SkeletonKing
- Diggerdude
- Posts: 176
- Joined: Sun May 13, 2007 11:32 am
- Location: Behind You
- Contact:
- SkeletonKing
- Diggerdude
- Posts: 176
- Joined: Sun May 13, 2007 11:32 am
- Location: Behind You
- Contact:
- SkeletonKing
- Diggerdude
- Posts: 176
- Joined: Sun May 13, 2007 11:32 am
- Location: Behind You
- Contact:
- SkeletonKing
- Diggerdude
- Posts: 176
- Joined: Sun May 13, 2007 11:32 am
- Location: Behind You
- Contact:
Well, my friend, that is not a good enough answer. If you could be more specific, then maybe we could track down the problem. But as it is, there is nothing wrong with this truck pack. I just ran all 28 trucks in clear whether and in pitch black and there are no errors.
<center><img src="http://mtm2.com/~trucks/P2007/21fitruck3pod28in1byonan.jpg"></center>
<center><img src="http://mtm2.com/~trucks/P2007/21fitruck3pod28in1byonan.jpg"></center>
- SkeletonKing
- Diggerdude
- Posts: 176
- Joined: Sun May 13, 2007 11:32 am
- Location: Behind You
- Contact:
- Drive2Survive
- Member
- Posts: 495
- Joined: Fri May 04, 2001 2:01 pm
- Location: Bathurst, NSW, Australia
- Contact:
Error like that typically means the texture is missing outright.
Did you unmount your original Truck2.pod, or leave it installed? BEARFOO1.RAW sounds like a texture from the stock game.
If the new truckpack pod doesn't have the BearFoot texture in it, then you'll need to keep Truck2.pod mounted as well.
Did you unmount your original Truck2.pod, or leave it installed? BEARFOO1.RAW sounds like a texture from the stock game.
If the new truckpack pod doesn't have the BearFoot texture in it, then you'll need to keep Truck2.pod mounted as well.
10 years of MTM2 ~ 1998-2008
"Thanks for the MTMories"
"Thanks for the MTMories"
Please notice in EJD's graphic that the RAW file being asked for is BEARFOO1.RAW whereas the truck pack uses renamed graphic files. Thus:
<center><img src="http://mtm2.com/~forum/images/topic4747.gif" width="600" height="416"></center>
Conclusion: if you are getting the BEARFOO1.RAW message than something else you have mounted is causing the error and not this truck pack.
<center><img src="http://mtm2.com/~forum/images/topic4747.gif" width="600" height="416"></center>
Conclusion: if you are getting the BEARFOO1.RAW message than something else you have mounted is causing the error and not this truck pack.
- Drive2Survive
- Member
- Posts: 495
- Joined: Fri May 04, 2001 2:01 pm
- Location: Bathurst, NSW, Australia
- Contact:
Ergo.
The FiTruck2.pod itself is not in error to 'not' contain the stock truck textures, but if you're treating it as a replacement for Truck2.pod you'll need to supply the stock textures to the game in some other way.
Edit: And I notice in your screenshot that the bins and trks keep the same filenames as the stocks even though the textures are different. I'll bet that Diggerdude's errors (he mentioned a TRK error) resulted from keeping the Truck2.pod mounted.
So if you ditch Truck2.pod, you run the risk of missing errors like EJD's, but if you keep it, you'll get conflicts. Moral of the story, ya can't win
That is, until you bring out the crowbar argument: http://ch.mtm2.com/c-pod/disable.php
I'm betting he saw it as a replacement for the stock trucks, so he discarded Truck2.pod from the pod.ini and replaced it with FiTruck2.pod. But now there's something else (most probably something in the track that he was trying to run) that needs the BEARFOO1.RAW.Drive2Survive wrote:Did you unmount your original Truck2.pod, or leave it installed?
The FiTruck2.pod itself is not in error to 'not' contain the stock truck textures, but if you're treating it as a replacement for Truck2.pod you'll need to supply the stock textures to the game in some other way.
Edit: And I notice in your screenshot that the bins and trks keep the same filenames as the stocks even though the textures are different. I'll bet that Diggerdude's errors (he mentioned a TRK error) resulted from keeping the Truck2.pod mounted.
So if you ditch Truck2.pod, you run the risk of missing errors like EJD's, but if you keep it, you'll get conflicts. Moral of the story, ya can't win
That is, until you bring out the crowbar argument: http://ch.mtm2.com/c-pod/disable.php
10 years of MTM2 ~ 1998-2008
"Thanks for the MTMories"
"Thanks for the MTMories"
Whatcha giving me a hard time for. You're speculating what these guys have done but they refuse to say themselves. I ran it with and without truck2.pod and with and without two other replacement pods simultaneously. What you say about other trucks needing what they've unmounted is likely the case, is in fact the case, but I've unlinked the review topic from the download because it misleads people into thinking things that are not true. And most newer uploads are not podzipped so there's equally likely the chance another pod has what they do not, and is equally likely there is a corrupt file in one of those pods. Has anybody except EJD given a specific error? No. Has anybody given us a pod.ini list? No. Has anybody looked for specific causes beside me? No. I will not condemn this truck pack based on what's here in this thread.
And yes, that http://ch.mtm2.com/c-pod/disable.php 's a sound argument.
And yes, that http://ch.mtm2.com/c-pod/disable.php 's a sound argument.
"That guy" made the original 2.1E J D wrote: I don't see what was wrong with the original MTM2.1, or why that guy had to upload it again.
- Drive2Survive
- Member
- Posts: 495
- Joined: Fri May 04, 2001 2:01 pm
- Location: Bathurst, NSW, Australia
- Contact:
Between this and the beta room you are in the wars, eh? 
Hey, I didn't say there was anything wrong with the truck pack myself or question your proof of soundness, which is thorough and should be the final word that this pack should (all other things being equal) work for anyone. I was just trying to cut to the chase of what the likely problem scenario for these guys was. My repeating the Truck2.pod question under your post was directed at them, not you, just as you have two posts arguing there is no error in the pack under one of mine.
Yes, these guys could be giving us more information to work from if they want a solution given.
No, I surely haven't downloaded and tried and inspected the thing myself.
Hey, I didn't say there was anything wrong with the truck pack myself or question your proof of soundness, which is thorough and should be the final word that this pack should (all other things being equal) work for anyone. I was just trying to cut to the chase of what the likely problem scenario for these guys was. My repeating the Truck2.pod question under your post was directed at them, not you, just as you have two posts arguing there is no error in the pack under one of mine.
Yes, these guys could be giving us more information to work from if they want a solution given.
No, I surely haven't downloaded and tried and inspected the thing myself.
Hmm, I may need to revise my conclusion above then.Phineus wrote:I ran it with and without truck2.pod
Really? I would have thought the other way. C-POD and BinEdit both podzip automatically when you build a pod with them. I don't know off the top of my head whether Traxx does now too; if it doesn't, then sure I can agree that most addons won't be podzipped when they're uploaded.Phineus wrote:most newer uploads are not podzipped
10 years of MTM2 ~ 1998-2008
"Thanks for the MTMories"
"Thanks for the MTMories"
