Hello
I recently made a B&O P5 reskin for a P7 model and everything was fine up until loading up MSTS. The game crashed and I have no idea why, I assumed I did something wrong with renaming the files but I followed the steps from every tutorial I could find and yet it still crashes my game. Is it an issue of poly count?
Jake
Engines crashing game
#2
Posted 20 October 2018 - 05:57 PM
You ask questions and don't provide any data. What files did you change? What is the poly count? What naming scheme did you use? Did the engine run in OR/MSTS before you made mods? Details man, details. Did you try OR to see if the log file offered any clues? If not give it a go and post the error log.
#3
Posted 20 October 2018 - 06:16 PM
Hello
So I tried the engine in OR to see if it worked and It did work in OR. It was a matter of poly count but the strange thing is that usually when a crash happens because of poly count, it gives me an error message that the poly count is to high but this time it wasn't.
I do apologize for not providing data, I'm just an idiot and I'm also very new to modeling in general.
Jake
So I tried the engine in OR to see if it worked and It did work in OR. It was a matter of poly count but the strange thing is that usually when a crash happens because of poly count, it gives me an error message that the poly count is to high but this time it wasn't.
I do apologize for not providing data, I'm just an idiot and I'm also very new to modeling in general.
Jake
#4
Posted 20 October 2018 - 07:47 PM
Jake:
In your first post, you said that you reskinned a B&O P5 to be a P7; is that correct?
If don't have access to the Loco's source files (which I assume you don't),
you only have the Loco's "Shape" (a.k.a. the .s file) and cannot change the Poly Count.
So, Poly Count may not be an issue.
If you have created new .ace file(s), with new names, the Loco's .s file must be edited
to call the new .ace files.
If MSTS encounters this issue, it generally refuses to load the model into the Sim.
ORTS is more forgiving; it will try to load the model, but will "gray-out" the textures it can't find.
Can you provide a list of the files that you changed to create the reskin?
BTW, you are NOT "an idiot"; you are new to modelling and there's a steep learning curve and many "traps" along the way.
Tutorials help, but you will learn by DOING; finding out what works and what doesn't.
I have been modelling for MSTS and ORTS for about 12 years and just learned something new tonite.
It is a constant learning experience; that's what makes it interesting.
In your first post, you said that you reskinned a B&O P5 to be a P7; is that correct?
If don't have access to the Loco's source files (which I assume you don't),
you only have the Loco's "Shape" (a.k.a. the .s file) and cannot change the Poly Count.
So, Poly Count may not be an issue.
If you have created new .ace file(s), with new names, the Loco's .s file must be edited
to call the new .ace files.
If MSTS encounters this issue, it generally refuses to load the model into the Sim.
ORTS is more forgiving; it will try to load the model, but will "gray-out" the textures it can't find.
Can you provide a list of the files that you changed to create the reskin?
BTW, you are NOT "an idiot"; you are new to modelling and there's a steep learning curve and many "traps" along the way.
Tutorials help, but you will learn by DOING; finding out what works and what doesn't.
I have been modelling for MSTS and ORTS for about 12 years and just learned something new tonite.
It is a constant learning experience; that's what makes it interesting.
#5
Posted 20 October 2018 - 07:55 PM
G-Man,
If you have ORTS on your system, try loading your model into it and see what the logfile says about it (you must, of course, have the logging option turned on). It will tell you far more than anything MSTS will tell you when it crashes
If you have ORTS on your system, try loading your model into it and see what the logfile says about it (you must, of course, have the logging option turned on). It will tell you far more than anything MSTS will tell you when it crashes
#6
Posted 20 October 2018 - 08:20 PM
You'll get completely different reasons for the same model crashing in MSTS than you will in OR.
My advice is don't bother w/ MSTS; It's ancient.
The suggestion on the OR log file is. essentially, do the required check. Always. If you suspect it's an .eng file problem be sure to examine all of the screens in the f5 display of OR for anything that should have a value greater than zero but doesn't.
My advice is don't bother w/ MSTS; It's ancient.
The suggestion on the OR log file is. essentially, do the required check. Always. If you suspect it's an .eng file problem be sure to examine all of the screens in the f5 display of OR for anything that should have a value greater than zero but doesn't.
#7
Posted 21 October 2018 - 04:30 AM
So I just did a test to see if the original model that I did the reskin from crashed my game as well and I was relieved that it wasn't just my reskin having issues. There's a problem with the model itself.
Also sandy, I didn't rename any of the files, I kept them for testing first so everything should be allised correctly.
Also sandy, I didn't rename any of the files, I kept them for testing first so everything should be allised correctly.
#9
Posted 21 October 2018 - 08:41 AM
It's Chris Van Wagoner's P7 on Trainsim.com. The filename is bo_p72.zip.
#10
Posted 21 October 2018 - 09:02 AM
Hi G-Man,
If the original B&O P7 is bo_p72.zip from trainsim.com, there is nothing wrong with the loco, as downloaded.
Cheers,
Ged
EDIT : Sorry, mate, our messages overlapped!! You should follow Dave's advice to run with Open Rails as you may get a better indication as to what's wrong with yours. Alternatively, re-download the file and retry the original.
If the original B&O P7 is bo_p72.zip from trainsim.com, there is nothing wrong with the loco, as downloaded.
Cheers,
Ged
EDIT : Sorry, mate, our messages overlapped!! You should follow Dave's advice to run with Open Rails as you may get a better indication as to what's wrong with yours. Alternatively, re-download the file and retry the original.