Quote:
Plas-D can be hit (and degraded using the 4:1 ratio) by non-phaser weapons, except ESG's which ignore them properly.
Undocumented feature? Bug? I don't think it matters much. Maybe a player-controlled Lyran PF might use Disruptors for anti-Plas-D duty. It's a harmless quirk in my book.
Anyways, 2.5.5.0 is superb. Great work, Taldren.
Quote:
Plas-D can be hit (and degraded using the 4:1 ratio) by non-phaser weapons, except ESG's which ignore them properly.
Undocumented feature? Bug? I don't think it matters much. Maybe a player-controlled Lyran PF might use Disruptors for anti-Plas-D duty. It's a harmless quirk in my book.
Anyways, 2.5.5.0 is superb. Great work, Taldren.
Quote:
So this is the LAST OP patch?
Quote:Quote:
So this is the LAST OP patch?
You know, they've never quite definitively said either way. I get the feeling it is the last, but anything could happen!
Quote:
My question goes what changed in the Shiplist file?
As always the patch loads a defualt version, and I don't don't just want to replace it with my models custom one with out knowing if it will change things I might need. It is a lot of work to redo it so I would please like to know if anything needs to be kept?
Quote:
Did you read the readme file? Right at the top, underneath the file description?
"Important Note: Make sure that the properties of your Orion Pirates
desktop shortcut shows the Target of your game pointing to the StarfleetOP.exe
file and that the Start In path is correct for your game install directory. "
Quote:
Yup did that before the patch and no luck on that.
Yes I actually do read those things and check before i patch good try though, NEXT!
Quote:
Yup did that before the patch and no luck on that.
Yes I actually do read those things and check before i patch good try though, NEXT!
Quote:
Ok this is just wierd if I launch the game using the SFCOP.exe it works fine the fighters load.
Bizare I tell you, don't ask i don't know why either...
Quote:Quote:
Ok this is just wierd if I launch the game using the SFCOP.exe it works fine the fighters load.
Bizare I tell you, don't ask i don't know why either...
Nothing bizarre or weird about it at all. When you run SFCOP it plays the intro movies and then runs StarfleetOP.exe with the working directory set correctly. When you bypass SFCOP and run starfleetOP.exe directly you have to define the working directory manually.
Quote:
You still have it wrong in your appreciation of the problem. What needs to be correct is the working directory, so that the game can find the ftrlist, not the path to the executable. If the path is wrong it just won't run. If the working directory is wrong then it won't be able to find any files that it expects to be in that working directory or it's sub-directories unless those locations are explicitly defined. This is not complex or mysterious or weird.
Quote:Quote:
You still have it wrong in your appreciation of the problem. What needs to be correct is the working directory, so that the game can find the ftrlist, not the path to the executable. If the path is wrong it just won't run. If the working directory is wrong then it won't be able to find any files that it expects to be in that working directory or it's sub-directories unless those locations are explicitly defined. This is not complex or mysterious or weird.
It's not?![]()
Quote:Quote:Quote:
You still have it wrong in your appreciation of the problem. What needs to be correct is the working directory, so that the game can find the ftrlist, not the path to the executable. If the path is wrong it just won't run. If the working directory is wrong then it won't be able to find any files that it expects to be in that working directory or it's sub-directories unless those locations are explicitly defined. This is not complex or mysterious or weird.
It's not?![]()
Do you think it is?
Quote:Quote:Quote:
You still have it wrong in your appreciation of the problem. What needs to be correct is the working directory, so that the game can find the ftrlist, not the path to the executable. If the path is wrong it just won't run. If the working directory is wrong then it won't be able to find any files that it expects to be in that working directory or it's sub-directories unless those locations are explicitly defined. This is not complex or mysterious or weird.
It's not?![]()
Do you think it is?
[Paths]
Maps = ".\MetaAssets\"
Scripts = ".\Assets\Scripts\"
Campaigns = ".\Assets\Scripts\Campaigns\"
[Files]
ShipSpecs = ".\MetaAssets\shiplist.txt"
FighterSpecs = ".\MetaAssets\ftrlist.txt"
CurMap = ".\MetaAssets\MiddleMap.mvm"
[Paths]
Maps = ".\MetaAssets\"
Scripts = ".\Assets\Scripts\"
Campaigns = ".\Assets\Scripts\Campaigns\"
[Files]
ShipSpecs = ".\Assets\Specs\shiplist.txt"
FighterSpecs = ".\Assets\Specs\ftrlist.txt"
CurMap = ".\MetaAssets\MiddleMap.mvm"
Quote:
Plas-D can be hit (and degraded using the 4:1 ratio) by non-phaser weapons, except ESG's which ignore them properly.
Undocumented feature? Bug? I don't think it matters much. Maybe a player-controlled Lyran PF might use Disruptors for anti-Plas-D duty. It's a harmless quirk in my book.
Anyways, 2.5.5.0 is superb. Great work, Taldren.
Quote:
Plas-D can be hit (and degraded using the 4:1 ratio) by non-phaser weapons, except ESG's which ignore them properly.
Undocumented feature? Bug? I don't think it matters much. Maybe a player-controlled Lyran PF might use Disruptors for anti-Plas-D duty. It's a harmless quirk in my book.
Anyways, 2.5.5.0 is superb. Great work, Taldren.
Quote:
So this is the LAST OP patch?
Quote:Quote:
So this is the LAST OP patch?
You know, they've never quite definitively said either way. I get the feeling it is the last, but anything could happen!
Quote:
My question goes what changed in the Shiplist file?
As always the patch loads a defualt version, and I don't don't just want to replace it with my models custom one with out knowing if it will change things I might need. It is a lot of work to redo it so I would please like to know if anything needs to be kept?
Quote:
Did you read the readme file? Right at the top, underneath the file description?
"Important Note: Make sure that the properties of your Orion Pirates
desktop shortcut shows the Target of your game pointing to the StarfleetOP.exe
file and that the Start In path is correct for your game install directory. "
Quote:
Yup did that before the patch and no luck on that.
Yes I actually do read those things and check before i patch good try though, NEXT!
Quote:
Yup did that before the patch and no luck on that.
Yes I actually do read those things and check before i patch good try though, NEXT!
Quote:
Ok this is just wierd if I launch the game using the SFCOP.exe it works fine the fighters load.
Bizare I tell you, don't ask i don't know why either...
Quote:Quote:
Ok this is just wierd if I launch the game using the SFCOP.exe it works fine the fighters load.
Bizare I tell you, don't ask i don't know why either...
Nothing bizarre or weird about it at all. When you run SFCOP it plays the intro movies and then runs StarfleetOP.exe with the working directory set correctly. When you bypass SFCOP and run starfleetOP.exe directly you have to define the working directory manually.
Quote:
You still have it wrong in your appreciation of the problem. What needs to be correct is the working directory, so that the game can find the ftrlist, not the path to the executable. If the path is wrong it just won't run. If the working directory is wrong then it won't be able to find any files that it expects to be in that working directory or it's sub-directories unless those locations are explicitly defined. This is not complex or mysterious or weird.
Quote:Quote:
You still have it wrong in your appreciation of the problem. What needs to be correct is the working directory, so that the game can find the ftrlist, not the path to the executable. If the path is wrong it just won't run. If the working directory is wrong then it won't be able to find any files that it expects to be in that working directory or it's sub-directories unless those locations are explicitly defined. This is not complex or mysterious or weird.
It's not?![]()
Quote:Quote:Quote:
You still have it wrong in your appreciation of the problem. What needs to be correct is the working directory, so that the game can find the ftrlist, not the path to the executable. If the path is wrong it just won't run. If the working directory is wrong then it won't be able to find any files that it expects to be in that working directory or it's sub-directories unless those locations are explicitly defined. This is not complex or mysterious or weird.
It's not?![]()
Do you think it is?
Quote:Quote:Quote:
You still have it wrong in your appreciation of the problem. What needs to be correct is the working directory, so that the game can find the ftrlist, not the path to the executable. If the path is wrong it just won't run. If the working directory is wrong then it won't be able to find any files that it expects to be in that working directory or it's sub-directories unless those locations are explicitly defined. This is not complex or mysterious or weird.
It's not?![]()
Do you think it is?
[Paths]
Maps = ".\MetaAssets\"
Scripts = ".\Assets\Scripts\"
Campaigns = ".\Assets\Scripts\Campaigns\"
[Files]
ShipSpecs = ".\MetaAssets\shiplist.txt"
FighterSpecs = ".\MetaAssets\ftrlist.txt"
CurMap = ".\MetaAssets\MiddleMap.mvm"
[Paths]
Maps = ".\MetaAssets\"
Scripts = ".\Assets\Scripts\"
Campaigns = ".\Assets\Scripts\Campaigns\"
[Files]
ShipSpecs = ".\Assets\Specs\shiplist.txt"
FighterSpecs = ".\Assets\Specs\ftrlist.txt"
CurMap = ".\MetaAssets\MiddleMap.mvm"