Topic: OP+ 3.2 Corrections Thread  (Read 19680 times)

0 Members and 1 Guest are viewing this topic.

FireSoul

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #120 on: January 24, 2004, 10:00:03 pm »
Quote:

Yep I had the pre-20th version.   I guess I missed there was a fix made to the earlier version.  Apparently others missed it as well.  




I'm not surprised. Can you make sure this knowledge is passed along if you encounter it too?

FireSoul

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #121 on: January 25, 2004, 02:19:00 pm »
A new opplus_32_no_models.exe installer has been generated. Enhancements include sanity checks and error popup messages when something seems wrong during models install/copy. No fixes were applied to the models themselves. Fetch and reinstall with this installer if you have any problems with past incarnations of the no_models installer.

 http://klingon.stasis.ca/OP_plusrefit/opplus_32_no_models.exe

-- Luc

FireSoul

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #122 on: January 26, 2004, 10:17:36 am »

.. btw.. I'm in the development process for version 3.2.1 (fixes and simple improvements release). It'll take some time since I touched up and modified about.. oh.. 96% of the model files.  In fact, I've been having problems with the new _brk.mod. For some reason, some _brk.mod files will make the game CTD. Not good.

Soo, last night, I started writing a skirmish .SCR which loads up a ship for a particular model, and blows it up.. and repeats the process, once per model used, for all ships within that race. Load a ship, blow it up.. load a ship.. blow it up.. .. Quite fun.



Fixes:
1- Fix my mistake about the speed 20 shuttles.

2- Fix a critical bug where if you try to use the batteries on a ship that has non, the game CTDs. (Further inspection demonstrates that ALL other units in the shiplist, planets and "BOX" included, have at least 1 Battery.)

3- Redid models. In fact, I reviewed them all .. modified the vast majority of them and created new break models for
them.
 Why? Because too much CPU power is wasted on models. Now, LODs (Levels Of Details) (at least 1 additional one) have been created for all models. .. also, why should I used the highest-poly model for the _BRK.mod? .. so I redid those with a lower # poly LOD as basis. This entire endeavour will take a lot of time, but will result in a more reasonable 'product'.
.. of course, the "no models" version is not affected by this.


-- Luc

Pestalence

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #123 on: January 29, 2004, 02:43:56 pm »
Using OP in combination of Firesoul's model checking script.... I found 2 errors...

L-DD

calssified as a DESTOYER when it needs to be DESTROYER

this was tested by editng in shipedit OP and used the dropdown menu. it listed DESTROYER and DESTOYER because it pulls the values from the shiplist... I selected DESTROYER and ren the script again.. it worked just fine and displayed the model.


F-AB

Taldren forgot to add Hull, UI and Ship Class

The ship class I assigned BASE STATION in shipedit OP's menu

The hull I made AB in Shipedit OP's dropdown menu

I set the UI to XAB in Shipedit OP's dropdown menu

doing this, the script found no errors on the models and no skipped entries...

Hope this helps and can't wait for the next version of OP +
 
« Last Edit: December 31, 1969, 06:00:00 pm by Pestalence »

FireSoul

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #124 on: January 29, 2004, 02:51:05 pm »
Quote:

Using OP in combination of Firesoul's model checking script.... I found 2 errors...

L-DD

calssified as a DESTOYER when it needs to be DESTROYER

this was tested by editng in shipedit OP and used the dropdown menu. it listed DESTROYER and DESTOYER because it pulls the values from the shiplist... I selected DESTROYER and ren the script again.. it worked just fine and displayed the model.


F-AB

Taldren forgot to add Hull, UI and Ship Class

The ship class I assigned BASE STATION in shipedit OP's menu

The hull I made AB in Shipedit OP's dropdown menu

I set the UI to XAB in Shipedit OP's dropdown menu

doing this, the script found no errors on the models and no skipped entries...

Hope this helps and can't wait for the next version of OP +, whether fixes or new...
 




thanks Pestalence..
.. I think the XAB is supposed to be 'SPECIAL'. I'll have to check within the stock shiplist. If it's set as BaseStation, you could probably do base installation missions with it. (eep?)

Pestalence

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #125 on: January 29, 2004, 02:57:38 pm »
The shiplist doesn't havve it classified as special.. just pointing to the XAB model.. so I just assigned the UI to XAB to match the model...

If you have Shipedit OP, then pull it up... it is the very first entry to load in the display...

there is no Hull listed.. so I gave it AB

There was no Ship Class Listed.. so I assigned Base Station (Astroid Base after all)

and I assigned the UI to match the default Model listed...

as far as SFB goes on Astroid Bases.. you can enter the role any way you wish according to your sources as Taldren's entries for role is blank..

I think they just used it instead of making a new UI and model for it...

it was simply overlooked and not a major part of the game.. however with these fixes to it.. I have tried some Single Player missions in astroids in Fed space while playing Klingon.. it is calling the Astroid base more... so I can't complain... works fine in game, at least with stock scripts.. haven't tried on the custom scripts.

Thanks.
 

Pestalence

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #126 on: January 29, 2004, 03:00:55 pm »
With that adjustment and no Role set for it .. it should show up in the bidding.. but haven't tested that far..
 

FireSoul

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #127 on: January 29, 2004, 03:22:46 pm »
that's the thing: it shouldn't be set up to come up for bidding.
.. SPECIAL is still best, imho.. especially since there's no such thing as a Asteroid Base in SFB.

FireSoul

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #128 on: January 29, 2004, 05:10:19 pm »
Quote:

1)  The Z-FLG should use a frigate model.  It's currently pointing to a destroyer model.  My master ship chart shows the Kzinti FLG uses a frigate hull.  I hope my list is up to date.




Done.

Quote:


Here are some personal comments clearly in the "opinion" category of things I'd like to see improved in the future.  This is very nit picky I know:

1)  Why not use Thu11's new skyhawk model to make a Sabrehawk by modding it to add an engine to the bottom?

2)  I hope Thu11 is making a Seahawk model.  Be nice to replace the taldren seahawk model with something in line with Thu11's series of rom models.

3)  Wish we had better Rom Vulture and Demonhawk models.

4)  Too bad Taldren didn't make Advanced FF models.  By the way, I'm glad you fixed the "X-refitted" hull stuff.  Great work.

5)  Man that Gorn "Advanced Destroyer" GDX model is so "out of character" with the Thu11 stuff.





1- saberhawk? Ah the SBH.. no.. I'll wait, for now. You can always make it.... The SBH has its own model slot.
2- Would be nice, yeah.
3- The Vulture is adequate, but of poor quality. The Demonhawk should like like some giant sparrowhawk/skyhawk half-breed..
4- what "X-refitted" stuff?
5- *shrug*

.. in all of the games where models are concerned, it's beyond my artistic ability to match what's already out there..
.. so.. I suggest you ask in the models forum.

 
« Last Edit: December 31, 1969, 06:00:00 pm by FireSoul »

FireSoul

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #129 on: January 29, 2004, 05:11:24 pm »
Quote:

Using OP in combination of Firesoul's model checking script.... I found 2 errors...

L-DD

calssified as a DESTOYER when it needs to be DESTROYER

this was tested by editng in shipedit OP and used the dropdown menu. it listed DESTROYER and DESTOYER because it pulls the values from the shiplist... I selected DESTROYER and ren the script again.. it worked just fine and displayed the model.


F-AB

Taldren forgot to add Hull, UI and Ship Class

The ship class I assigned BASE STATION in shipedit OP's menu

The hull I made AB in Shipedit OP's dropdown menu

I set the UI to XAB in Shipedit OP's dropdown menu

doing this, the script found no errors on the models and no skipped entries...

Hope this helps and can't wait for the next version of OP +
 




Fixes completed.

FireSoul

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #130 on: January 29, 2004, 05:13:04 pm »
All of the recent fixes above have not been released yet. This will have to wait till the next release.. however, at my end's devel version, it's done.

-- Luc

Chris Jones

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #131 on: January 31, 2004, 10:09:37 pm »
Hi Firesoul.

Fired up 3.2, 1st Skirmish I tried showed a missing model.

check the plr folder in OPPLUS/Models.   My download has no files in it.

I verified the path with shipedit.

 
Upon further investigation the following folders have no files as well.

par
pcr
pdw
ppr
pslv
« Last Edit: December 31, 1969, 06:00:00 pm by Chris Jones »

FireSoul

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #132 on: January 31, 2004, 11:56:53 pm »
Hm. Tried reinstalling?

Chris Jones

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #133 on: February 02, 2004, 06:17:37 am »
Well that's odd.

I installed the files to another directory to look them over first.. In the cut and paste I did to put them in the right place those folders lost files..

Re-install made it all better.

 

FireSoul

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #134 on: February 02, 2004, 09:43:32 am »
Quote:

Well that's odd.

I installed the files to another directory to look them over first.. In the cut and paste I did to put them in the right place those folders lost files..

Re-install made it all better.






Ah-ha. Ok. I understand what happened.
.. See, these models are probably the ones COPIED from SFC:OP stock over to the OPPLUS directory. Until I have better models for these ships, these are placeholders for model separation.
.. other ships affected would have been a few police ships. Why?

ie: IPOL model. model copied from :IFF.
Difference? My model.siz lists the IPOL to be smaller than the IFF, allowing a difference.


In future installations, I'll add something.. maybe a small textfile that says "copied from assets/models/$MODEL" in the directories of stuff copied over. We'll see.

FireSoul

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #135 on: February 02, 2004, 09:46:21 am »
I need SFB-knowledgeable advice


I have made an error: I have commissioned ships, lyran and fed tugs, with 3 cargo pods. Someone has lately told me that there are supposed to be only 2 pods max on these ships, and that the 3rd pod weight notice on the SSD is just in case one of the 2 other pods is a double-weight pod.
.. similarly, the gorn tugs would have only 1 pod.

.. can someone confirm this for me? If this is true, than I have some ships to *delete*.

jimmi7769

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #136 on: February 02, 2004, 04:14:33 pm »
Quote:

I need SFB-knowledgeable advice


I have made an error: I have commissioned ships, lyran and fed tugs, with 3 cargo pods. Someone has lately told me that there are supposed to be only 2 pods max on these ships, and that the 3rd pod weight notice on the SSD is just in case one of the 2 other pods is a double-weight pod.
.. similarly, the gorn tugs would have only 1 pod.

.. can someone confirm this for me? If this is true, than I have some ships to *delete*.  




The Fed tug could carry 3 all in a row as long as they were single weight pods(eg cargo, starliner, etc)  I think it was the only one that could haul 3.  The Klingon, Kzinti, and Romulan could carry 2 and no more.  The Gorn could carry 2 as well as the Lyran and Hydran but if they did the pods capability was serverly limited.  Like a Lyran Tug with a Battlepod and a cargo pod couldn't use the pods disruptors.  The ISC tug was like the Klingon and could only carry 2 and I think it had to always carry 2 for balance purposes.

Hope this helps.

FireSoul

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #137 on: February 02, 2004, 04:28:57 pm »
Quote:

Quote:

I need SFB-knowledgeable advice


I have made an error: I have commissioned ships, lyran and fed tugs, with 3 cargo pods. Someone has lately told me that there are supposed to be only 2 pods max on these ships, and that the 3rd pod weight notice on the SSD is just in case one of the 2 other pods is a double-weight pod.
.. similarly, the gorn tugs would have only 1 pod.

.. can someone confirm this for me? If this is true, than I have some ships to *delete*.  




The Fed tug could carry 3 all in a row as long as they were single weight pods(eg cargo, starliner, etc)  I think it was the only one that could haul 3.  The Klingon, Kzinti, and Romulan could carry 2 and no more.  The Gorn could carry 2 as well as the Lyran and Hydran but if they did the pods capability was serverly limited.  Like a Lyran Tug with a Battlepod and a cargo pod couldn't use the pods disruptors.  The ISC tug was like the Klingon and could only carry 2 and I think it had to always carry 2 for balance purposes.

Hope this helps.  




It does. It means I did things right on the first try.
Where'd you come across this information, pray tell?

jimmi7769

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #138 on: February 02, 2004, 04:42:41 pm »
Quote:

Quote:

Quote:

I need SFB-knowledgeable advice


I have made an error: I have commissioned ships, lyran and fed tugs, with 3 cargo pods. Someone has lately told me that there are supposed to be only 2 pods max on these ships, and that the 3rd pod weight notice on the SSD is just in case one of the 2 other pods is a double-weight pod.
.. similarly, the gorn tugs would have only 1 pod.

.. can someone confirm this for me? If this is true, than I have some ships to *delete*.  




The Fed tug could carry 3 all in a row as long as they were single weight pods(eg cargo, starliner, etc)  I think it was the only one that could haul 3.  The Klingon, Kzinti, and Romulan could carry 2 and no more.  The Gorn could carry 2 as well as the Lyran and Hydran but if they did the pods capability was serverly limited.  Like a Lyran Tug with a Battlepod and a cargo pod couldn't use the pods disruptors.  The ISC tug was like the Klingon and could only carry 2 and I think it had to always carry 2 for balance purposes.

Hope this helps.  




It does. It means I did things right on the first try.
Where'd you come across this information, pray tell?  




R Sections, tug/pod special rules and so forth.  Let me dig my books out to be sure.

look at annex 3a

I was wrong Fed can only carry 2 which would mean none can carry more than 2 but the double weight pods make it move like it has 3.    Hydran has a cargo pod built in and can only carry one other pod.
« Last Edit: February 02, 2004, 04:58:04 pm by jimmi7769 »

FireSoul

  • Guest
Re: OP+ 3.2 Corrections Thread
« Reply #139 on: February 04, 2004, 12:37:18 am »
Quote:


R Sections, tug/pod special rules and so forth.  Let me dig my books out to be sure.

look at annex 3a

I was wrong Fed can only carry 2 which would mean none can carry more than 2 but the double weight pods make it move like it has 3.    Hydran has a cargo pod built in and can only carry one other pod.




"No tugs can carry 3 pods'. Gotcha. .. heh.. for the first time, I think the next revision of OP+ might have less ships in the list.
.. But that's okay, I think. No one never really see these, no matter if they're errors or not.

-- Luc