Latest Graphic Designs

[Armand2REP]

Is everyone else getting the main gun to rotate?

[steel_selachian]

There is a mistake in the .bat file.... it should say FA_FREMMfr.J3d and not FA_FREMM.J3D... my bad.... I will never rush to release something again :S

Sorry guys,
Fox

P.S. Here is something to make up for it, check the picture :)
1059


Pfft, minor hiccup. Ooh, Sea King and Merlin ... while you're on those, one of my top helicopter requests is the CH-53 (CH-53K would be ideal). Right now I'm using the posted HH-3E model for those.

FCCC, while we're posting airstrip records, do you have the ones for the Garibaldi model?

[Saffron]

Any chance of getting an Mi-8 model? They're rather prolific on the Warsaw Pact side.

[Saffron]

And no, I wasn't able to get the main gun to rotate, either, but it fires, which is the important thing. :cool:

[steel_selachian]

Any chance of getting an Mi-8 model? They're rather prolific on the Warsaw Pact side.

As an interim I've been using FoxAlfa's model for the Westland Puma for the Mi-17 and Mi-8. Not an exact fit, but much better than the 19.01 use of the FC Huey model.

[FoxAlfa]

As an interim I've been using FoxAlfa's model for the Westland Puma for the Mi-17 and Mi-8. Not an exact fit, but much better than the 19.01 use of the FC Huey model.

I am making a Soviet pack.... it will include SS-N-7,9,12,14,19,27, Kh-31, MiG-21, MiG-29, Su-15, Mi-8, Mi-14, R-27 and R-77 models.
Missiles are done, now I need to start on the aircraft....but you know modeling takes time, a lot of time...

Cheers,
Fox

[FoxAlfa]

And no, I wasn't able to get the main gun to rotate, either, but it fires, which is the important thing. :cool:

About the Gun on FREMM... my moving parts are exactly the same as in Read me

1. PROP01 spd = -4 Y = 1 Continuous
2. PROP02 spd = 4 Y = 1 Continuous
3. radar01 spd = 2 Z = 1 Continuous
4. radar02 spd = 2 Z = 1 Continuous
5. radar04 spd = 2 Z = 1 Continuous
6. radar03 spd = 6 Z = 1 Continuous
7. 76mm Controlled
8. 20mm_p Controlled
9. 20mm_s Controlled

The launcher record order on my FRAMM is and the record for the 76mm Launcher is 1061http://forums.navalwarfare.net/attachment.php?attachmentid=1060&d=1298717379

It most work, since its the exeacliy the same model. Redo it... if you not, you will just have to wait for the 19.02 :S

Cheers,
Fox

[Fleet Command CC]

That would be a big help. Thanks

Hello sepperson.

The reason why you can't find the model's in question is because there not in that .rar file I uploaded. I thought that they was in it, sorry about that I will upload the missing models for you soon.

[Fleet Command CC]

To all that are having problems getting the main gun to rotate on the FREMM, the gun is rotating but its not showing up in the graphics. This is how it will look in the next release of NWP.

Me and Mike D talk about this about five to six years ago, and Mike D decided that it would be too much work to edit all the gun launchers, just for some eye candy. I haven't talk to Warrior about this so I dunno how he would feel about changing all the gun launchers.

I can't post the info on how to fi this issue, because I'm not on the computer with the files needed, but I will post the info has soon has I can.;)

[Saffron]

If I knew how to fix it, I could probably go through and edit all the gun launchers, then I could just send you and Warrior the appropriate files for the next release. I have the time on my hands to do that.

[Saffron]

I can go through all the gun launcher records and edit them if people want me to. I certainly have the time. Then I can mail the appropriate files to you (FCCC) and Warrior for the next release. I just need to know how to do fix the rotation issue.

One other question: Since NWS is no longer officially working on FC and this seems to now be a "private" venture, does the rule about not making country-specific skins for models still apply? Since it's pretty easy to clone a model and change its .j3d file in the db editor (and some nations already have their own entry for specific aircraft), I wouldn't mind seeing some different skins for widely used aircraft.

[steel_selachian]

I can go through all the gun launcher records and edit them if people want me to. I certainly have the time. Then I can mail the appropriate files to you (FCCC) and Warrior for the next release. I just need to know how to do fix the rotation issue.

One other question: Since NWS is no longer officially working on FC and this seems to now be a "private" venture, does the rule about not making country-specific skins for models still apply? Since it's pretty easy to clone a model and change its .j3d file in the db editor (and some nations already have their own entry for specific aircraft), I wouldn't mind seeing some different skins for widely used aircraft.

Well, I think the main issue behind that aside from driving the NWP staff nuts was the size of the update - more skins means more .j3d and .bmp files, and a bigger installation file. With some aircraft like the F-4 and F-16 that are used by a lot of nations, that can get a little wacky. Then again, they are useful in certain circumstances. I've said repeatedly that when I see an Iranian F-14 in a US paint job I half expect the ground crew to burn the plane on the runway :p

[Saffron]

If I remember correctly, the only reason why the NWS staff didn't want to deal with separate paint jobs for each nation was because it was a lot of work editing the database. For instance if you have 10 countries using a STK, STK*, STK^, and STK~ version of the same aircraft, that's 40 entries in the database just for that particular variant. If you add all the AAWs, SEADs, TNKs, SUWs, etc., for that same variant, say an F-16C-50, you could end up with hundreds of entries for just the F-16C-50.

Since I doubt any graphic designer working on FC would ever come anywhere close to putting out a separate skin for each plane in each country, I doubt it would ever escalate to that level. But if these reskinned models were released as individual downloads (like the current models in this thread) instead of being included in an installation file, we could choose whether we wanted to do the editing work. If we don't want to, we don't have to use them.

[Fleet Command CC]

I can go through all the gun launcher records and edit them if people want me to. I certainly have the time. Then I can mail the appropriate files to you (FCCC) and Warrior for the next release. I just need to know how to do fix the rotation issue.

One other question: Since NWS is no longer officially working on FC and this seems to now be a "private" venture, does the rule about not making country-specific skins for models still apply? Since it's pretty easy to clone a model and change its .j3d file in the db editor (and some nations already have their own entry for specific aircraft), I wouldn't mind seeing some different skins for widely used aircraft.

Hello Saffron.

Well if it was just down to me I wouldn't have a problem with you doing it but, you will aft to wait and see what Warrior thinks about it.
You also are going to need to buy some software to help you do this task. Went I get to my other computer I will let you know how to fix the gun rotations.

On the country-specific skins yes it still apply, unfortunately because that is where a lot of bug's come from, and also what you and steel_selachian have said too.
Its just easier to have one base skin for all. ;)


!!!Edited!!! : its too late dunno what I'm typing here I hope it reads right now.

[Fleet Command CC]

If I remember correctly, the only reason why the NWS staff didn't want to deal with separate paint jobs for each nation was because it was a lot of work editing the database. For instance if you have 10 countries using a STK, STK*, STK^, and STK~ version of the same aircraft, that's 40 entries in the database just for that particular variant. If you add all the AAWs, SEADs, TNKs, SUWs, etc., for that same variant, say an F-16C-50, you could end up with hundreds of entries for just the F-16C-50.

Since I doubt any graphic designer working on FC would ever come anywhere close to putting out a separate skin for each plane in each country, I doubt it would ever escalate to that level. But if these reskinned models were released as individual downloads (like the current models in this thread) instead of being included in an installation file, we could choose whether we wanted to do the editing work. If we don't want to, we don't have to use them.

If there are people that are willing to re-skin a model and get it posted on the forum then that would be great for all in opinion. Why don't you have a try at re-skining some of the models I've posted. :cool:

[Fleet Command CC]

Hey Saffron.

Have a try at re-skinning the F-14 Tomcat that I posted on the (Some models you can download and add yourself) thread. Check out the one that is on the first post at the end of that posted.

[Saffron]

I have no idea how to do skinning work, unfortunately, and I probably don't have the appropriate software. My funds for computer expenditures (i.e. software) is rather limited right now. But if it can be done with freeware and there is a good place to learn how to do it, I might give it a try.

[FoxAlfa]

On the country-specific skins yes it still apply, unfortunately because that is where a lot of bug's come from, and also what you and steel_selachian have said too.
Its just easier to have one base skin for all. ;)

Honestly, I think on this it should be more on case pre case base, Like most of the F-16 look the same anyway...so Generic model is ok, on the other side if you have too diameterly opposed sides, Like US and Iran with the same equipment (but different load-outs) we could make a exception now and then, like its already done in the NWP...

Cheers,
Fox

[Fleet Command CC]

To all wanting to know.

I've anwsered the question on how to fix the Main gun on my How too's thread, beacuse this thread is for the latest models not a Q&A thread. ;)

Any other problems please post them on the How too's thread.

To Saffron.

I will post some info for you to have a go at skinning a model soon.

To Fox.

Yep that sounds ok to me.

[steel_selachian]

Two things about that last batch of items from FoxAlfa:

1) What was the problem with the Oscar's props? They looked fine to me.

2) Has anyone else tested using the Exocet Block III on land targets? I tried it once and the missiles stuffed right into the deck once they crossed the shore and hit higher terrain.

[FoxAlfa]

Two things about that last batch of items from FoxAlfa:

2) Has anyone else tested using the Exocet Block III on land targets? I tried it once and the missiles stuffed right into the deck once they crossed the shore and hit higher terrain.

Missile type: Terrain Following on?

[steel_selachian]

Missile type: Terrain Following on?

Good call, I'll give that a whirl.

[Fleet Command CC]

Two things about that last batch of items from FoxAlfa:

1) What was the problem with the Oscar's props? They looked fine to me.

2) Has anyone else tested using the Exocet Block III on land targets? I tried it once and the missiles stuffed right into the deck once they crossed the shore and hit higher terrain.

Hello steel_selachian.

I thought there was something wrong with the left propeller, but there isn't I was just using the wrong name. :o :D

[steel_selachian]

Hello steel_selachian.

I thought there was something wrong with the left propeller, but there isn't I was just using the wrong name. :o :D

Yes, conveniently enough it appears the part names are the same as the existing FC Oscar model. Makes life easy.

[FoxAlfa]

Yes, conveniently enough it appears the part names are the same as the existing FC Oscar model. Makes life easy.

Yep, I started using the FC naming standard...

[steel_selachian]

One request I'd like to make is a new Seawolf SSN - kinda hurts to see such a lousy model of my favorite sub in-game. I'm trying to see if (although this is probably one of those "can't put it in an NWP release" things) I can decompress the 3d.ndx file of my Sub Command copy and sub in that game's Seawolf (actually got it to work, but then I did something else and ended up overwriting it with the old model and can't figure how to get it back).

[Fleet Command CC]

One request I'd like to make is a new Seawolf SSN - kinda hurts to see such a lousy model of my favorite sub in-game. I'm trying to see if (although this is probably one of those "can't put it in an NWP release" things) I can decompress the 3d.ndx file of my Sub Command copy and sub in that game's Seawolf (actually got it to work, but then I did something else and ended up overwriting it with the old model and can't figure how to get it back).

Hey steel_selachian.

Just re-compress the .j3d file from Sub Command into the Fleet Command 3d.grp file, I've got a nice model of the Seawolf somewhere, I will find it you.

[steel_selachian]

Thanks. I might also try renaming the .j3d file to see if that works.

Speaking of sub graphics, I've been trying to figure out if the 688-class subs actually have the vertical fins at the ends of the stern planes (supposed to be supports for the towed-array sonars). They're missing on all the drydock photos I've seen of 688s and in the case of the 688Is it looks like they have the sonar dispensers mounted on small angled fins like the Seawolf and Virginia classes.

http://navsource.org/archives/08/500/0869118.jpg

http://www.navsource.org/archives/08/0871104.jpg

http://www.navsource.org/archives/08/0875317.jpg

http://www.navsource.org/archives/08/0877201.jpg

http://www.navsource.org/archives/08/0877330.jpg

[Fleet Command CC]

Yes I did Thank you. Sorry for the late response, been busy tweeking this thing. Played a few times and have enjoyed the "fixes" and add-ons. Still can't locate the great graphic files for the Virginia Class CGN and the Iwo Jima class LPH as well as the Tarawa.

Hello sepperson.

Here are linwg00 Models.

CH-46E TRN
CH-53D TRN
California CGN
Virginia CGN
SA-10abc Grumble
Iwo Jima LPH
Typhoon RAF
Forrest Sherman DD
Bainbridge CGN
Bainbridge CGN(70)
Decatur DDG
Barry DD (1967)
Zhdanov CLC
Senyavin CLC
Shershen MTB
Tu-22BD STK Blind
Tarawa LHA(80)

I have only included the .J3D and .bmp files and two .bat that I have made, you will find to two .zip folder in the linwg00 Models from 08082009.zip

One is for ATI, GMA, nNIDIA Gpu's and the other is for 3DFX Gpu's & 3DFX Emulators.

PLEASE SCAN THE DOWNLOADED FOLDERS BEFORE EXTRACTING THEM, WITH ANY GOOD ANTI-VIRUS AND SPYWARE PROGRAM!!! ITS JUST BETTER TO BE SAFE THAN SORRY, I ALWAYS DO THIS WITH ANY FILES OR FOLDERS I DOWNLOAD!!! :)

**Disclaimer** -- Electronic Arts Jane’s Combat Simulations, and Sonalysts, Inc. are not supporting any modifications made by the end users. This is at your own risk. Please do not call or email their customer support for help with these files. These model's, files, programs & info are in no way connected to, or affiliated with the Developers of Fleet Command Sonalysts, Inc, its employees, representatives, consortium's, or other persons or companies associated with it. Therefore the creators of these model's, files, programs & info will take no responsibility for harm that it might do to your game or computer by trying them.

Also this NWS forum will take no responsibility for harm that these items might do to your game or computer by trying them.

It as not harmed my game or computer but use these items at your own RISK OK.

These models are not to be used in any other games or programs without prior consent or permission from the NWP team!!!

By downloading these zip folder's on this thread you are agreeing that you have READ and UNDERSTOOD the Disclaimer!!!

If you would like to try this model you can download it from this link below.

Click here to Download (http://www.filefactory.com/file/cac8d6c/n/linwg00_Models_from_08082009.zip)

[Fleet Command CC]

Thanks. I might also try renaming the .j3d file to see if that works.

Speaking of sub graphics, I've been trying to figure out if the 688-class subs actually have the vertical fins at the ends of the stern planes (supposed to be supports for the towed-array sonars). They're missing on all the drydock photos I've seen of 688s and in the case of the 688Is it looks like they have the sonar dispensers mounted on small angled fins like the Seawolf and Virginia classes.

http://navsource.org/archives/08/500/0869118.jpg

http://www.navsource.org/archives/08/0871104.jpg

http://www.navsource.org/archives/08/0875317.jpg

http://www.navsource.org/archives/08/0877201.jpg

http://www.navsource.org/archives/08/0877330.jpg

Hey steel_selachian.

No probs, re-naming the model will work fine just remember to compress the rename .J3d file into, the 3d.grp file and change the name in the 3D object records in the data base. This is always something I forget to do. :o

[steel_selachian]

Hey steel_selachian.

No probs, re-naming the model will work fine just remember to compress the rename .J3d file into, the 3d.grp file and change the name in the 3D object records in the data base. This is always something I forget to do. :o

Didn't decompress it and it didn't work, even though I had changed the 3D Object record in the db. If you have that other Seawolf model I'd like to have a look-see and just put that in; quite frankly I like having the model files uncompressed so I can have everything out where I can see it.

[Fleet Command CC]

Didn't decompress it and it didn't work, even though I had changed the 3D Object record in the db. If you have that other Seawolf model I'd like to have a look-see and just put that in; quite frankly I like having the model files uncompressed so I can have everything out where I can see it.

The re-named (or any other new) file must be compress into the 3d.grp, or it will never work in the game. The uncompressed files in the Graphic folder are not used by the game they are basically temp files, they are only needed in the Graphic folder so they can be compress into the 3d.grp after that they can be delete if you so wish too. ;)

[steel_selachian]

The re-named (or any other new) file must be compress into the 3d.grp, or it will never work in the game. The uncompressed files in the Graphic folder are not used by the game they are basically temp files, they are only needed in the Graphic folder so they can be compress into the 3d.grp after that they can be delete if you so wish too. ;)

Really? So just running the cmputil.exe 3d in DOS won't do it? In that case, how the heck do all the other add-ons I put in work?

[Fleet Command CC]

Really? So just running the cmputil.exe 3d in DOS won't do it? In that case, how the heck do all the other add-ons I put in work?

I'm not sure what your asking here?

What won't work?

Has I said in the other post once the .J3D and .bmp files have been compress in the 3d.grp they are not needed in the Graphic folder.

All the other models work because you've compress them into the 3d.grp file.

[Saffron]

Really? So just running the cmputil.exe 3d in DOS won't do it? In that case, how the heck do all the other add-ons I put in work?

I think what FCCC is saying is that, once you compress the graphics files into the 3d.grp by using DOS, the graphics files can be deleted. It's like copying a file to a zip file. Once you've compressed the copy into the zip, you can delete the original since a copy of the file is now compressed into the zip file. Compressing a graphics file into the 3d.grp creates a copy of the graphics file, making the files you actually downloaded and placed into your graphics folder redundant. That is why, if you change the name of a graphics file, you have to recompress it into the 3d.grp. Otherwise, the game won't recognize the new name.

[Fleet Command CC]

I think what FCCC is saying is that, once you compress the graphics files into the 3d.grp by using DOS, the graphics files can be deleted. It's like copying a file to a zip file. Once you've compressed the copy into the zip, you can delete the original since a copy of the file is now compressed into the zip file. Compressing a graphics file into the 3d.grp creates a copy of the graphics file, making the files you actually downloaded and placed into your graphics folder redundant. That is why, if you change the name of a graphics file, you have to recompress it into the 3d.grp. Otherwise, the game won't recognize the new name.

Hey Saffron.

You understand me then, thanks for explaining it another way. :cool:

[Armand2REP]

We need a base model that can be used for Eurocopter Tiger, AW Mangusta, HAL LCH, and the Harbin Z-10.

[steel_selachian]

I think what FCCC is saying is that, once you compress the graphics files into the 3d.grp by using DOS, the graphics files can be deleted. It's like copying a file to a zip file. Once you've compressed the copy into the zip, you can delete the original since a copy of the file is now compressed into the zip file. Compressing a graphics file into the 3d.grp creates a copy of the graphics file, making the files you actually downloaded and placed into your graphics folder redundant. That is why, if you change the name of a graphics file, you have to recompress it into the 3d.grp. Otherwise, the game won't recognize the new name.


Gotcha. I may wait until FCCC has coughed up the code for that second batch of ling's models and possibly that Seawolf model he mentioned, though. If I'm going to do file compression I might as well get all the birds in one package.

[Fleet Command CC]

Gotcha. I may wait until FCCC has coughed up the code for that second batch of ling's models and possibly that Seawolf model he mentioned, though. If I'm going to do file compression I might as well get all the birds in one package.

Hey Steel.

I've send you the password, about the Seawolf model its from DW (Dangerous Waters) but it won't work if you just copy it from DW. The model needs to be edited before it will work in FC.

[Saffron]

Hmm, what models are on linwg's second batch? I'm not sure if I have them or not.

[Fleet Command CC]

Hmm, what models are on linwg's second batch? I'm not sure if I have them or not.

Hey Saffron.

I think you have got them they are the ones that you had problems with using the 3DFX Emulator, from the FC20090808.rar linwg's first batch, that he posted on this thread. :cool:

CH-46E TRN
CH-53D TRN
California CGN
Virginia CGN
SA-10abc Grumble
Iwo Jima LPH
Typhoon AAW* sead*stk^~suw^
Typhoon AAW sead stk+suw
Forrest Sherman DD
Bainbridge CGN
Bainbridge CGN(70)
Decatur DDG
Barry DD (1967)
Zhdanov CLC
Senyavin CLC
Shershen MTB
Tu-22BD STK Blind
Tarawa LHA(80)

[Saffron]

Ahh yes, I do have them - thanks FCCC. :)

[steel_selachian]

Got the new batch put in - looks nice. Suggestions on moving parts and airstrips?

Only critique is that the RAF Eurofighter seems to have the canards set too far aft, but we already have BlimpCommander's model to use.

[Saffron]

What I did was use linwg's database folder (should be included in the zip file), looked up the new units, took screen shots of moving parts, airstrips, launchers, etc. then created a new unit entry in my own database folder and carefully entered all of linwg's information. It's time consuming and a PITA, but that's how I did it.

If your database is a standard database without your own tweaks and modifications, you can just swap your database file with the one included.

[sepperson]

Thank you, email sent for the password.

[Fleet Command CC]

What I did was use linwg's database folder (should be included in the zip file), looked up the new units, took screen shots of moving parts, airstrips, launchers, etc. then created a new unit entry in my own database folder and carefully entered all of linwg's information. It's time consuming and a PITA, but that's how I did it.

If your database is a standard database without your own tweaks and modifications, you can just swap your database file with the one included.

Hey Saffron.

Steel won't be able to do that because there is only the .J3D and .bmp also .bat files included in my download link.


Thank you, email sent for the password.

Hey sepperson.

I've send you the password. :cool:

[steel_selachian]

Hey Saffron.

Steel won't be able to do that because there is only the .J3D and .bmp also .bat files included in my download link.


Actually, it looks like most of what I want those for is in the earlier file he put up that was a complete set of FC files ... holy blowchunks, Batman, there was a lot more in there than was listed! I'm still figuring out what all the goodies are.

[sepperson]

Got the password and the ships look great. Love the new H-46 and H-53's too. One issue, not sure if its me, but some of the guns and missile launchers that are aft are facing forward. Plus the radars don't seem to rotate on the California. Also, with the Iwo Jima, the bow wake of the ship is to far forward and the helo's when coming up on deck appear "off" the deck and appear out of no where. Is there some tweaking I need to learn? The new ship graphics are fantastic! Anyone out there have a better looking A-6 Intruder?

[Fleet Command CC]

Got the password and the ships look great. Love the new H-46 and H-53's too. One issue, not sure if its me, but some of the guns and missile launchers that are aft are facing forward. Plus the radars don't seem to rotate on the California. Also, with the Iwo Jima, the bow wake of the ship is to far forward and the helo's when coming up on deck appear "off" the deck and appear out of no where. Is there some tweaking I need to learn? The new ship graphics are fantastic! Anyone out there have a better looking A-6 Intruder?

Hello sepperson.

Check your email inbox it should help you out. :cool:

[steel_selachian]

Got the password and the ships look great. Love the new H-46 and H-53's too. One issue, not sure if its me, but some of the guns and missile launchers that are aft are facing forward. Plus the radars don't seem to rotate on the California. Also, with the Iwo Jima, the bow wake of the ship is to far forward and the helo's when coming up on deck appear "off" the deck and appear out of no where. Is there some tweaking I need to learn? The new ship graphics are fantastic! Anyone out there have a better looking A-6 Intruder?

I've been begging for a good A-6 and now we have it. Frankly what I want to see now are a USN F-8 Crusader, A-1 Skyraider, and E-1 Tracer. Do that and we'll have the whole Vietnam airwing.

Just asking, that big .rar file with all the database info did have an install file for all those models right? And is everything in there a complete working model?

[Saffron]

Hmm there's a new A-6 floating about? Any chance I could snag it? Oh, and is that Mirage 2000 available yet?

[steel_selachian]

Hmm there's a new A-6 floating about? Any chance I could snag it? Oh, and is that Mirage 2000 available yet?

http://forums.navalwarfare.net/showthread.php?44-Latest-Graphic-Designs/page46

There's a lot more stuff in here than FCCC listed in the update text file. A-4B, A-6A, a new A-7 in Navy colors, new Q-5, JH-7, new F-15E, F-100, Tu-128 Fiddler, Tu-22 Blinder, two new Tu-16 models, new Echo, Foxtrot, Romeo, and Tango sub models, new Enterprise CVN, and other goodies. Only problem is without a batch file it looks like I'll have to track the dang things down and add them manually.

[Saffron]

Ah okay, I have all of those in my game then. It's been awhile since I've used those aircraft. Thanks.

[sepperson]

There were A-6's and A-7's in that download. I haven't been able to use that one because it would have replaced all the work I have done. Wish they were available individually.

[Armand2REP]

Oh, and is that Mirage 2000 available yet?

I am sure Fox Alpha well get to it when he can. Looking forward to that Mistral BPC too.

Did anyone get that awesome Garibaldi model to work? I never did see a link to download it.

[steel_selachian]

I am sure Fox Alpha well get to it when he can. Looking forward to that Mistral BPC too.

Did anyone get that awesome Garibaldi model to work? I never did see a link to download it.

I know there's a skin for it in that .rar file, but I don't know if the actual .j3d model was there.

[Saffron]

If I remember right, the only thing needed to make the Garibaldi to work was to change a single letter in one of the file names, but I don't remember which file (.bmp or .j3d) or which letter it was.

[steel_selachian]

If I remember right, the only thing needed to make the Garibaldi to work was to change a single letter in one of the file names, but I don't remember which file (.bmp or .j3d) or which letter it was.

I got that info from FCCC, but that .rar file he posted has a "scafo.bmp" file that looks like a much more highly detailed skin. I just don't know if it has a model it goes with.

[Fleet Command CC]

If I remember right, the only thing needed to make the Garibaldi to work was to change a single letter in one of the file names, but I don't remember which file (.bmp or .j3d) or which letter it was.

Hey Saffron.

Something I remember finding out, just change one of the two file names, Garbaldi.bmp or Garibaldi.BMP. To GARIBALD.bmp and that will stop the CTD.

[Fleet Command CC]

I got that info from FCCC, but that .rar file he posted has a "scafo.bmp" file that looks like a much more highly detailed skin. I just don't know if it has a model it goes with.

Hey steel_selachian.

That is the Garibaldi CV Two, the picture is on post #404, the model works in the game but can be a bit CTD sometimes. I never did finish getting it to work in the game well, move on to other models.

Fox might make us a new one if you ask him nicely. :cool:

[steel_selachian]

Just asking, what else was in that .rar file? I got suspicious and checked the doctrine folder that came in it and saw there's something like 18 new files in it. Was that thing the full-blown 19.02 update complete with new units and doctrines? If so I may just accept starting over on my personal edits and working with the new one. Some things like the ITALD and the new doctrine for the SS-N-27 I've been waiting to see for a while.

[Fleet Command CC]

Just asking, what else was in that .rar file?.

Hey steel.

There are quite a few new things in that .rar file. :)


I got suspicious and checked the doctrine folder that came in it and saw there's something like 18 new files in it. Was that thing the full-blown 19.02 update complete with new units and doctrines?

Its only part of NWP19.02 release, I might post a beta soon just waiting to see what Warrior think about it. :cool:


If so I may just accept starting over on my personal edits and working with the new one. Some things like the ITALD and the new doctrine for the SS-N-27 I've been waiting to see for a while.

I would wait and till the latest version is release, before you start doing your personal modding. ;)

[steel_selachian]

Yeah, I checked it over and didn't see some of the units advertised for 19.02 that I was particularly interested in (A+ series of iron bombs, ITALD, etc.). So I'll stick with my current 19.01 modifications and Frankenstein in the new stuff for now.

FCCC, if you're interested I could see about compressing my database edits and sending them along. Most of the ones I made are units I'd like to see in future NWP releases. Among other things I added the Permit and Skipjack-class SSNs to the US, as well as separating the Narwhal out into her own class due to the extensive quieting mods she had.

Has anyone else had occasional CTD issues with some of the new models? It doesn't happen when I click on them, but sometimes when I go to F3 and move teh camera around or exit a mission while the camera is on the unit in question.

[O.K.]

Yeah, I checked it over and didn't see some of the units advertised for 19.02 that I was particularly interested in (A+ series of iron bombs, ITALD, etc.). So I'll stick with my current 19.01 modifications and Frankenstein in the new stuff for now.

FCCC, if you're interested I could see about compressing my database edits and sending them along. Most of the ones I made are units I'd like to see in future NWP releases. Among other things I added the Permit and Skipjack-class SSNs to the US, as well as separating the Narwhal out into her own class due to the extensive quieting mods she had.

Has anyone else had occasional CTD issues with some of the new models? It doesn't happen when I click on them, but sometimes when I go to F3 and move teh camera around or exit a mission while the camera is on the unit in question.


Hey Steel.

I was able to get the new database from Havoc, who was asked to check the sensors work in upcoming release. I added a few new entries to it that have not yet been included, but I would like to see them in future. I sent modified db to Havoc to continue work on sensors and asked him to send it back to Warrior, who may accept or reject my changes. But Havoc admitted to me yesterday that he wasn't working with sensors yet.

So I think we maybe combine our efforts to make satisfactionary db with all new entries needed for new scenarios. If it is in agreement with NWP policy, I can send You new (projected for 19.02) db with my new entries, so You can add what in Your opinion should be included in futre version of NWP. I also send You list of my changes (in txt file), and I will ask You to add description of all the changes You will make, in that file (I think that all changes should be recorded). Then You will resend it to me and I send it to Havoc or Warrior. Final acceptance or rejection of all changes is up to Warrior, in accordance with NWP policy.

I don't want to make any competitive mod to that of NWP, so main problem is coordination nad agreement. Otherwise we finish with 2-3 different databases.

[Fleet Command CC]

FCCC, if you're interested I could see about compressing my database edits and sending them along. Most of the ones I made are units I'd like to see in future NWP releases. Among other things I added the Permit and Skipjack-class SSNs to the US, as well as separating the Narwhal out into her own class due to the extensive quieting mods she had.

Hey Steel.

At the moment the answer is no I'm sorry to say, because its best that only one person does the db editing. Not only that if we do it for you we will need to do it for all which isn't going to work.

Saying that if you explain in detail what you've done on the Sticky: Fleet Command How-to's", it could be add to a future release but I'm not going to guarantee it will be added.


Has anyone else had occasional CTD issues with some of the new models? It doesn't happen when I click on them, but sometimes when I go to F3 and move teh camera around or exit a mission while the camera is on the unit in question.

Which models and from what Data Base, if it is from your own modded db files you may have done something wrong some where.

[steel_selachian]

Hey Steel.

At the moment the answer is no I'm sorry to say, because its best that only one person does the db editing. Not only that if we do it for you we will need to do it for all which isn't going to work.

Saying that if you explain in detail what you've done on the Sticky: Fleet Command How-to's", it could be add to a future release but I'm not going to guarantee it will be added.



Which models and from what Data Base, if it is from your own modded db files you may have done something wrong some where.

Yeah, I figured something like that. I was just wondering if some of the non-fancy stuff I put in would be useful as a starting point, like the GBU-53 SDB II, KDX-III DDG for South Korea, Atago- and Hyuga-class for Japan, etc. I'm not really keen on messing with fiddly bits like sensors and doctrines, and the stuff I've done for aircraft weapons configurations are personal preferences and I'll keep it that way (although I've noticed that as of 19.01 there were some serious errors on the F/A-35 weapons, such as stuff mounted on stealth-configured aircraft that wouldn't fit in the weapon bays).

The models I'm seeing issues with are the ones from that .rar file - the Tu-16A and C ones seem to cause it a lot, but I also see it on the F-15E and Echo-II as well as some others. I'll be playing a test scenario, select a unit, go to F3 and pan around the unit for a good look, and blot. Or I'll exit out of the scenario and crash the game. I thought I got all the various skin bits integrated into the batch file I wrote ...