KJakker

Guys, I have finally gotten around to putting together the F-106 cockpit frame workaround with an add-on cockpit INI file, ReadMe File, and screen caps, and I am almost ready to upload it. However where should I upload it to? After all this is not a full Cockpit, just a cockpit.ini file and a ReadMe file with additional instructions. Should I still upload it to Add-On Cockpits → Jet Cockpits or should it go in the Object Mods → ini File Edits section? Second, I need to credit the the original creator of the F-106A_COCKPIT.INI file that I based this mod off of. Below are the credits included in the F-106A Delta Dart for SF2 V1.02 which list the 3D Model by Pasko and the Cockpit by Kesselbrut. Does that mean that the Cockpip.INI file was by Kesselbrut? I would really like to cite the source file I worked from correctly. Credits: 3D Model: Pasko Cockpit: Kesselbrut Avionics: Column5, eburger68, DaniloE31 Data.ini: Column5, eburger68, DaniloE31 Loadout & loading images: DaniloE31 Hangar image: MKSheppard holes.tgas: eburger68 Textures: Sundowner Decals: Dave, DaniloE31 Weapons Model: Pasko (I think?! Please rectify me in case…) Weapons Data: DaniloE31 Aerial Nuke Effect: Lexx Luthor Beta Test: 76.IAP-Blackbird

Weird, all of yesterday my joystick was not recognized by any computer in my house even after reboots, updates, and all of the other things I tried and yet today I plugged it in and the computer recognized it without issue. I just reset the control settings in SF2 now that the stick is detected again and flew an intercept mission and downed three bombers in an F-102 without issue. I don't know exactly what was going on. The only thing I can think of is something that I read while trying to troubleshoot the issue late yesterday night. I found out that the SideWinder Precision 2 is the only joystick of the SideWinder family to have a steel base plate. Apparently a side effect of this feature is that it can cause a build up of static electricity in the stick that disrupts the signal passing through the cable between the stick and the computer. According to the post if the stick is left unplugged for several hours this static charge will dissipate and restore the stick to proper operation. I just find it odd that in all of the years that I have had this joystick I never encountered such an issue before. Still stick is working again so that is all I care about. Thank for all of your comments.

Well today my Microsoft SideWinder Precision 2 Joystick that I have had for, I think, fifteen years seems to have finally died on me. I was testing some aircraft data file and weapons mods in SF2. The instant my test mission finished loading the aircraft went into an uncommanded role to the right and I was forced to Ctrl-Alt-Del out of the game. After that the game did not recognize the joystick which prompted me to check windows which showed that the stick was not detected by the OS but the port I had the joystick plugged into detected a flash drive just fine. I have run the Windows Hardware and Devices troubleshooter and tried plugging the stick into multiple USB ports on three different computers to no effect. I don't know if it is the USB plug or an internal component that has failed. Any advice other than buying a new Joystick?

I have been aware of the unit for years, but then I am from the USA and US WWII history is one of my hobbies.

View File CL/CLAA-119 Juneau Class ------------------------------------------------------ USS Juneau Class Cruiser Ver 1.0 ------------------------------------------------------ By YEYEYE & KJakker. --------------- DESCRIPTION --------------- This is the CL-119/CLAA-119 Juneau Class Light AA Cruiser modeled by YEYEYE. It includes both an early and a late version. The CL-119 represents the USS Juneau CL-119, USS Spokane CL-120, and USS Fresno CL-121 when equiped with the 40mm Bofors. The CLAA-119 represents the USS Juneau CLAA-119 after its November 1951 to February 1952 overhaul which replaced the 40mm mounts with 3inch/50caliber Mark 33 gun mounts. Note: Three "Data.INI" files for the CL-119 Juneau class and two for the CLAA-119 Juneau class have been included. The AltGuns1 and AltGuns2_DATA.INI variants use alternate guns from the default file; these guns can be found in the Optional Files\Optional Guns folder. Also in the Optional Files\Optional Data Files folder you will find subfolders titled Structural Factor x2, Structural Factor x3, and Structural Factor x4, and Default Data File Backup as I was not sure how strong players would want the ship to be. Each version has a Structural Factor that many times that of the Default variant. --------------- SPECIAL NOTE --------------- This package was assembled at the request of Do335. --------------- INSTALLATION --------------- Backup anything in your SF2 Mods folder that you think may be effected. Extract all the files from the archive to a safe place on your harddrive then take the folder labled "To Mods Folder" and copy it into your Strike Fighters 2 mods folder, overwrite as needed. Optional Files If you want to use the alternate guns that the AltGuns1 and AltGuns2 data file variants are set up for then afte doing the above go to Optional Files folder and move the contents of the Optional Effects, Optional Guns, Optional Sounds folders to their respective folders in your Mods folder. Then add the data from the Sound List Additions.txt to your SOUNDLIST.INI folder. --------------- CREDITS --------------- Ship basic model, Distance-LODs, and Skins by YEYEYE. Data and Names INI files as well as the Hull names and numbers for the Spokane and Fresno are by KJakker. The included optional guns listed below are by KJakker. 20MM_L70ww 20MM_L70wwL 40MM_L56 40MM_L56L 3IN_MK22_TF 5IN_38_MK12_AA Guns below were originaly from the "Guns Collection for SF2 Series 2.0" by FLOGGER23. 20MM_L70 40MM_L60 Most of the included effects are by Stary. The two Effects listed below are by KJakker and are based upon work by Stary & Thirdwire. 76mmFlakEffect LtTankGunFireEffect Do not distribute, repackage or post without consent from YEYEYE & KJakker. No Modifications without previous consent is allowed. And this is freeware, it must not be used in any commercial product. Copyright ? YEYEYE, KJakker. All rights reserved. --------------- Special thanks. --------------- Thirdwire and TK for their sim and some instruments. Hope you enjoy it. YEYEYE & KJakker July 2016 =========================================================== Submitter KJakker Submitted 07/27/2016 Category Cruisers

It's not April 1st, did some one misread their calendar?

http://combatace.com/topic/85359-sarcasm-20-beta-by-stary/page-3?do=findComment&comment=700133 http://combatace.com/topic/85359-sarcasm-20-beta-by-stary/page-3?do=findComment&comment=700177 http://combatace.com/topic/85359-sarcasm-20-beta-by-stary/page-3?do=findComment&comment=700178

Take a look at this video.

I found this while following some news links. http://www.houstonchronicle.com/neighborhood/cyfair/news/article/Firefighters-bid-farewell-to-last-known-9-11-7966974.php?t=8d7faea17b438d9cbb&cmpid=twitter-premium#photo-10201552

Navy: Human error to blame for March cable break aboard USS Eisenhower flight deck

It is in the ObjectData001.CAT file. Just extract it with Mue's CATExtractor. Edit: My mistake, I missed that this is for SF1.

I found the quote below in the caption of another copy of the video. "Eight sailors were injured aboard the USS Eisenhower when an arresting cable snapped during an E-2C Hawkeye's landing in March 2016."

Derk, you might want to take a look at the link below. http://combatace.com/topic/87422-modified-aim-120c-that-will-drop-from-the-f-22-f-35-weapons-bay/#entry705739

Okay, I just tried this out. Below are two pairs of screenshots taken in the same single mission in SF2 comparing my Windows 7 desktop and a Windows 10 laptop both with Mue's distance fix in place. Detail setting in game us Unlimited. EnvironmentSystem.ini Sky setting used. FlightEngine.ini Scene Clip and Detail Option settings used. Windows 7 Desktop Windows 10 Laptop Windows 7 Desktop Windows 10 Laptop

I ask about the ENVIRONMENTSYSTEM.INI in case there was something in it that could be interfering. Make sure that the SkyDistance= in the environmentsystem.ini is greater than the FarClipDistance= in the flightengine.ini. Just to check, did you put the .fx files into every single one of your terrain folders? Next what are the settings you are using in your flightengine.ini? The ones below are what I am presently using. [backgroundSceneClip] /FarClipDistance=240000.0 FarClipDistance=160000.0 NearClipDistance=3000.0 [ForegroundSceneClip] FarClipDistance=14000.0 NearClipDistance=0.45 [insideSceneClip] FarClipDistance=250.0 NearClipDistance=0.01 [LowDetailOption] //HorizonDistance=30000.0 /HorizonDistance=90000.0 HorizonDistance=60000.0 /DetailMeshSize=6 DetailMeshSize=9 DetailLevel=0 WaterEffect=0 NoiseTexture=0 MaxTextureRes=128 [MedDetailOption] /HorizonDistance=42000.0 //HorizonDistance=126000.0 HorizonDistance=84000.0 /DetailMeshSize=6 DetailMeshSize=9 DetailLevel=1 WaterEffect=1 NoiseTexture=0 MaxTextureRes=256 [HighDetailOption] /HorizonDistance=50000.0 //HorizonDistance=150000.0 HorizonDistance=100000.0 /DetailMeshSize=9 DetailMeshSize=14 DetailLevel=2 WaterEffect=2 NoiseTexture=1 MaxTextureRes=512 [unlimitedDetailOption] /HorizonDistance=62000.0 //HorizonDistance=186000.0 HorizonDistance=124000.0 DetailMeshSize=18 DetailLevel=2 WaterEffect=2 NoiseTexture=1 MaxTextureRes=-1

FalconC45, would you please attach your FLIGHTENGINE.INI and ENVIRONMENTSYSTEM.INI files for us to look at? Also are you using any terrain mods and if so which ones? Edit:What Stary said also.

I have all of the SF2 titles and I checked the Version.ini file and it is okay. The odd thing is that Mue's LODViewer sees the LOD just fine, it is only in game that they don't show.

I am with you Erik. I have liked that story ever since I first read it.

Does anyone know what is going on here? I thought at first that it was an error I made with Skyraider mods, but after I removed all the A-1 folders from the mods folder for SF2 and replaced them with stock folders and ini files extracted from the CAT's the problem still persist.