Fubar512

It should be saved inside the weapons folder. Once you've clicked save, you're done. Make sure that there's also a file named "weapondata.dat", time and date stamped to when you saved the data.

It's not complicated. You need to use the proper version of the weaponeditor to VALIDATE the weapondata.ini. You do so by opening it with the (and I cannot stress this often enough) proper version of the weaponeditor, and then saving it with same. That's all.

Congrats!

It never went below 35 FPS, and averaged 40+. As an encoded WMV file, it's a constant 30 FPS, so I've made my point. I purposely panned the view the way I did in order to deceive the viewer's eye. And it's SF2, using Stary's CE Terrain and the Mirage Factory's MiG-29A.

?

Yes

Only the "BoosterSoundName" entry works reliably. Sustainer sounds and inflight sounds only work sporadically, if at all. As for the effect, you'll either need to point to an existing missile inflight effect, or create a new one. And, in order to answer the acceleration question, you must supply at least one more piece of data. Acceleration cannot be determined from terminal velocity, alone.

Getting waaaay colder

Nope. 1) No stutters 2) Guess again

Anyone care to estimate the frame rate on this video? FPS.wmv

Actually Streak, I've not experienced any appreciable degradation in accuracy until the frame rates dropped into the teens.

Oh No! Not the dread 396 kilometer diameter bomb issue! Anything but that!

Sometime ago, one of the gamer sites ran an E-article on frame rates, or rather, people's perceptions of frame rates. To do this, they showed three different videos to a test group. The first video showed a character running through an otherwise featureless landscape. The second showed the same character shooting at, and dodging fire from opponents. The final video sequence was that of a scorched earth scenario with huge explosions, flames, falling wreckage, and characters fleeing for their lives. They then asked which had the highest frame rate. Most people selected the first (the character running through the featureless landscape. They choose wrong The vid with the fastest frame rate, was the one most people had voted the slowest, and that was the scorched earth vid (the third one). They came to the conclusion that the overwhelming majority of people cannot perceive the difference between a video at 30 fps, and one at 100+. The quest for insane frame rates was started by gamers who played first person-shooters, back in the DOS and Windows 9X days, when frame rates were directly tied to mouse refresh and reaction rates. That basically became a moot point around the time that games were being written for Windows XP and DX9.

That weapons pack predates the '08 patch. All you need to do is download and install this weapon editor: http://www.thirdwire.net/files/dl/WeaponEditor_022008.zip And then follow the instructions in the knowledge base here: http://combatace.com/topic/12210-getting-the-weapon-editors-to-work-in-winxp/ and here: http://combatace.com/topic/9323-adding-weapons-to-sfwovwoe-a-tutorial/

Yes, it's quite flat

Mach 1 is Mach 1. It varies with temperature and altitude. ThirdWire is using the "standard day" value.

The most-often ignored advice when it comes to computers: "Back up, back up, back up!" All my downloaded TW titles are backed up twice. First, on to an external HDD, and then, onto a DVD.

As the lod file is cotained within the cat file, and is read by default from that location, how can it be corrupt? Again, on a default TW model, you do not need to extract the lod file...you just need to direct the .ini to it, as outlined above.

What would your issue have to do with the cat file containing that model? Just copy the following data into the B-57B.ini file contained within its like-named subfolder in your mod folder, and then save it. [AircraftData] AircraftFullName=B-57B Canberra AircraftShortName=B-57 AircraftDataFile=B-57B_data.ini LoadoutFile=B-57B_loadout.ini UserList=B-57B_UserList.ini [LOD001] Filename=B-57B.lod Distance=120 [LOD002] Filename=B-57B_lod002.lod Distance=400 [LOD003] Filename=B-57B_lod003.lod Distance=800 [LOD004] Filename=B-57B_lod004.lod Distance=2000 [LOD005] Filename=B-57B_lod005.lod Distance=12000 [DamageTexture] DamagedPostFix=_holes.DDS [shadow] CastShadow=TRUE ShadowCastDist=10000 MaxVisibleDistance=800 [TextureSet001] Directory=USAFCamo1 Name=USAF Camo 1 T.O. 1-1-4 Nation=USAF Squadron=8BS Specular=0.400000 Glossiness=0.400000 Reflection=0.000000 [TextureSet002] Directory=USAFSilver1 Name=USAF Silver 1 Nation=USAF Squadron=13BS Specular=1.000000 Glossiness=0.500000 Reflection=0.800000 [TextureSet003] Directory=USAFBlack1 Name=USAF Black 1 Night Intruder Nation=USAF Squadron=8BS Specular=0.800000 Glossiness=0.500000 Reflection=0.200000 [TextureSet004] Directory=RAFCamo1 Name=RAF Camo 1 Nation=RAF Specular=0.400000 Glossiness=0.400000 Reflection=0.000000

Happy Birthday, Monty

Pretty much, as longs as it contains all the necessary gun types tha NF calls for.

They're called out on a file by file-name basis, in the gundata.ini

Yes, values on one side should mirror those on the other, and, that FM is not SF2 friendly. Try mirroring the first set, keeping in mind that the stall values are somewhat optimistic, and that the Ymac for a left side surface is always expressed as a negative value, while that for the right surface is always a positive value (think of X,Y,Z coords, and you'll understand).

There is both an APU-62R and an APU-62L (right and left) in one of the earlier weapons packs.

The red tide.........airborne dinoflagellates....