Leaderboard
Popular Content
Showing most liked content on 01/27/2025 in all areas
-
8 pointsGood morning, First of all, I hope everyone is doing well. I would like to apologize to all Developers, News Staff, Moderators, Administrators, Founders, Principles and the many members of this site. I made an honest mistake by downloading more mods that I was entitled to in a matter of hours. This happened around 2 weeks ago. I am an honest person and I own my Fuckups, and this is a serious one. Please be certain that ALL the outstanding mods that I downloaded are for my own and exclusive use. I recently purchased Strike Fighters 2 and wanted to get it up to speed. Looking pretty and with more campaigns to play. No other intensions were the cause of this fiasco I created. As for myself, I got what I deserved. I got banned from this site. Please accept my humble apology. That's all I am begging for everyone to do. The original message was written and posted this morning. I am not the sharpest knife in the kitchen, and honestly think I posted it on the wrong place. I know a lot of FLAK is coming my way. I am aware it is well deserved. Thank you all for all your hard work and for keeping all these flight simulators alive. GOD BLESS. Respectfully, Reyes, Ricardo SFC, USA, Ret. 19K4K8
-
7 points
-
3 pointsi had a good day today and i got the early version of the F-4D cockpit done , it is still a BETA version but for everybody who likes to test it here it is PLEASE backup your ini files before overwriting it with this new ones PLEASE let me know if you have any problem with FPS drop or any other problems and on what terrain F-4D.7z the following ini files are changed and needed to get the cockpit working F-4D_Data.ini F-4D_Cockpit.ini F-4D_Loadout.ini F-4D_Avionics.ini on the right side panel you will find the DSU-94/A nuke control panel , if you load a nuke and this panel is not working check if the weapon you loaded is listed on the bottom of the Cockpit.ini and if it is not listed just add it to the list , after that the DSU-94/A panel should work if you find any problems or errors please let me know , this is still a BETA have fun , ravenclaw_007
-
2 pointsThat actually solved my issues with HUD_LCOS!!! I can finally have working gun and rocket depression in AA and AG mode in HUD! You just saved me tons of works! Cheers!
-
2 pointswell chit. forgot i left that in there i see your heavy ordinance and raise 64 troopers on a one way trip
-
2 pointspppuuhhh..... i´m happy that the problem was found , Thank you so much will change it right away on my aircraft
-
2 points
-
2 points
-
1 pointBit of a treat today! Polovski himself descended from the heavens to hold court and talk about all things WOFF and flight sims and even a bit about old brown dogs! So pull up a stool, grab a pint and have a listen! I think it would be great if they did this more often, I learned a lot!
-
1 pointThis is such a treat to listen to! Thanks so much for putting this together Rick - been wanting to hear from OBD for a long time! Enjoyed the interview with a fine cup of coffee. Cheers to you all!
-
1 point
Version 1.0.0
63 downloads
This is my C-130 Hercules Megapack. It includes all the files for the 48 versions of the C-130 Hercules listed below: AC-130A ---------------- USAF SEA Camo AC-130A_83 ------------- USAF Gunship Grey AC-130H ---------------- USAF Euro1 Camo, USAF Gunship Grey AC-130H_93 ------------- USAF Gunship Grey AC-130H_04 ------------- USAF Dark Grey AC-130J ---------------- USAF Dark Grey AC-130U ---------------- USAF Dark Grey AC-130U_04 ------------- USAF Dark Grey AC-130W ---------------- USAF Dark Grey C-130A ----------------- RAAF Silver, USAF Silver C-130A (Roman nose) ---- USAF Silver C-130B ----------------- USAF SEA Camo C-130E ----------------- RAAF Grey/White, USAF Euro1 Camo, USAF SEA Camo C-130E(I) -------------- USAF Blackbird Camo Light Grey Underside C-130E (SKE) ----------- USAF Euro1 Camo, USAF SEA Camo C-130E (SKE & ASE)------ USAF Grey C-130H2 ---------------- RAAF Camo C-130H2 (ASE) ---------- RAAF Camo, RAAF Dark Grey C-130H3 ---------------- USAF Dark Grey C-130H-30 -------------- French Camo C-130J (ASE) ----------- RAAF Grey, RAAF Dark Grey (fictional) C-130J-30 (ASE) -------- RAAF Grey, RAAF Dark Grey C-130K ----------------- RAF Camo Light Grey Underside, RAF Camo C-130K (ASE) ----------- RAF Camo, RAF Green C-130K-30 -------------- RAF Camo Light Grey Underside, RAF Camo C-130K-30 (ASE) -------- RAF Camo, RAF Green CC-130H (SAR) ---------- RCAF Dark Grey DC-130A ---------------- USAF SEA Camo DC-130A_USN ------------ USN Grey/White/Yellow DC-130E ---------------- USAF SEA Camo EC-130H ---------------- USAF Grey HC-130P ---------------- USAF SEA Camo KC-130F ---------------- USMC Grey KC-130H ---------------- Spanish Desert Camo KC-130J ---------------- USMC Grey KC-130J (Harvest HAWK) - USMC Grey KC-130R ---------------- USMC Grey KC-130T ---------------- USMC Grey L-100-30 --------------- Kuwait Grey/White MC-130E ---------------- USAF Blackbird Camo, USAF Euro1 Camo MC-130E_92 ------------- USAF Dark Grey MC-130E_04 ------------- USAF Dark Grey MC-130H ---------------- USAF Euro1 Camo, USAF Dark Grey MC-130H_04 ------------- USAF Dark Grey MC-130J ---------------- USAF Dark Grey MC-130P ---------------- USAF Dark Grey MC-130P_12 ------------- USAF Dark Grey MC-130W ---------------- USAF Dark Grey Please read the readme file (included) for installation instructions and credits. Dels -
1 pointStill working on the ADC Variations....I think they're looking better! 184th TFG ADC Variation 1: 184th TFG ADC Variation 2:
-
1 point@ravenclaw_007 in F-4D_67_DATA.ini in the [DetectSystem] section, I found that HasRWR=FALSE must be setting on TRUE. Now it works. I found the same in F-4D_71_DATA.ini so I checked the stock [...]_DATA.ini and it's set on TRUE.
-
1 pointOne thing to try with the rwr issue is the format you are saving the rwr image as. I can't speak to photoshop or gimp because I use paint.net but I have had an issue where a radar screen image was saved with a parameter changed that made it not show up in the game. Also those with a problem could try bmp or jpeg format to see if one works over the other.
-
1 pointThanks, but wasn't the TEWS later on though? I mean it's neat but not time correct if I understand correctly.
-
1 pointok i just made the changes and notice that the Type=VECTOR has a frequency setting , maybe that is one of the problems , i just removed the frequency entry and the RWR was still working , maybe you can try that as well or change the LoBandsMaxFreq to 0.2 and the HiBandsMinFreq to 20 LoBandsMaxFreq=4.0 HiBandsMinFreq=8.0 in case this is not working , here is the F-4D_67 cockpit with Type=TEWS , just drop the RWR folder in to the cockpit folder and let the avionics.ini overwrite the existing one F-4D_67 TEWS.7z
-
1 pointyap , i have to make some changes to it , will take some time to do it because i have some doctor apointments in the next days
-
1 pointthe F-4D_78 uses Type=TEWS for the RWR and the F-4D_67 uses Type=VECTOR so i looks like as i f you have aproblem with the Type=VECTOR , the entry is the same as the original TW so i dont know what to do
-
1 pointcould you delete this entry on top in the Avionics.ini RadarTextureSize=512 has nothing to do with the RWR display but who knows i checked the entrys for the RWR it is exactly the same as the standard TW , so will start working on the Radar settings
-
1 pointThanks will check it , but the entrys are more or less the same as the standard ones except for the radar size will see what i can do
-
1 point
-
1 pointU.S. ARMY OH-13 Sioux, 9th Cav Regt. 1st Squadron, South Vietnam1966
-
1 pointthe early F-4D/E did not have any option for the ripple Quantity , even the late F-4D´s do not have any switch in the cockpit for the Ripple quantity but i set them on the F-4D_78 to 1,2,18 cockpits are still BETA and i do have to make some more changes and fix some issues this is the F-4D_78 cockpit , i made a lot of changes on this one , the weapon selector is now working with EOGB and dispensers like CBU-2 (picture on the bottom ) had to make some work around to get it done the SRI indicator ( slanted range indicator ) is only showing the distance to the next way point , unfortunatley no other options in SF2 the LOS indicator ( line of sight for laser targeting pods ) is not working , i try that but i dont get i done the way it should be , so it is just a eye candy for now , maybe in the future i will find a way here is the new F-4D_78cockpit F-4D_78.7z pictures from the cockpit CBU-2 dispenser selected
-
1 point
-
1 point
-
1 point
-
1 pointEasteregg in my Rio de la Plata terrain. The Llama is a little bit to big, but who cares.
-
1 pointThanks , but it is strange , here is everything functioning over nord vietnam
-
1 pointHi Volks, Hi Eagle114th, i'm also tweak with some Avionics and Radar Screens since years. Specialy F-4, A-6, Tomcat and F/A-18C. I want to upload it as my own, but these great Mod is worth to bring all the stuff together! F-4B eary Radarscreen F-4C Early F-C 67
-
1 pointIf you're in that big of a hurry, you can go first......
-
1 point...and just for grins and giggles after FINALLY figuring out how the TOD editor works, I've been looking over the India-Pakistan map, and rearranging the fugly TODs that I've hated from day one!! A major improvement in being able to have building ACTUALLY follow the street grid and not be all over the map (pun intended). Also will let me fix a bunch of things I never go right the 1st time
-
1 pointthis is the F-4D_71 cockpit with early RWR display and Threat warning panel F-4D_71.7z did anybody test one of this cockpits ??? how about the FPS any impact on it ???
-
1 pointHello everyone! While working on A-4, I realized I would like to start wokriongon K-14 computing gyro gunsight first, since both uses same shapes. However, what I realize is taht in SF2, there is no methods of expanding / shriniing of the circular gunsight, therefore, there are two version of K-14 gunsight for F-51s, F-80s, etc.. Before i show the screenshot, I also noted that originally K-14 have 6 of diamond shape dots surrounding the dot at center. However, when the diamond moves away or toward the center, the diamond start to become thinner. Here is video that shows this: (Starting at 0:50) By finding the balance between thin 'line' and diamond shape, here is 25 MILs version of K-14: is 50 MILs version: And here Anyone will have the options to use either 25 MILs or 50 MILs version. Now next, for main (caged) gunsight, there are three version: Crosshair, K-14A, and K-14B. By using HUD, you will bea ble to toggle between Crosshair only or K-14A, as well Crosshair only and K-14B, depending ona ircraft. For preview purpose, I put K-14 and crosshair together os you can get idea what it looks like: Next, K-14A with K-14 computing gunsight. NOTE: According to the flight manual, K-14A is 70 MILs) Next, K-14B and K-14 computing gunsight: Eagle114th
-
1 pointDora's Over Dhimar Avia S-190D Luňák - 1st Fighter Regiment, Parani Army Air Force, 1946
-
1 pointthis is the F-4D cockpit from 1967 with an early RWR display but still without the threat warning panel , its for the F-4D_67 F-4D_67.7z and here is an other update for the F-4D cockpit lod , just drop it in to the F-4D cockpit folder and let overwrite if ask to F-4D_67_Cockpit.LOD all animation should work now , canopy close / open , Hook lever and the Landing Gear lever should work if not let me know
-
1 pointjust found that some parts are not proberly linked and thats why they did not show up , here is the fixed lod just drop the lod in to the cockpit folder and let overwrite if ask to F-4D_67_Cockpit.LOD
-
1 pointNight Intruder North American Mustang IB (A-36A) - No.1 Squadron, RAF Fighter Command, 1943
-
1 pointEagle114th, Try first by adding 'ShowAnyWeapon=TRUE' there in avionics.ini: [HUD_LCOS] SymbolType=LCOS ShowAnyWeapon=TRUE that should be enough to fix the pb of the sight being visible for rockets (and bombs, if any). Additional note: the gunsight image call in the avionics.ini NAV mode is probably redundant: [HUDModeNav] Symbol[01]=HUD_GUNSIGHT Symbol[0]= .../... [HUD_GUNSIGHT] SymbolType=IMAGE ImageFilename=cockpit\A-1CM_SIGHT.TGA //ImagePosition=0,0.0555 ImageSize=0.0675 You already have it from the call in the cockpit.ini ("GunsightName=A-1CM_SIGHT.tga"). You probably have the 2 sights superimposed in NAV mode. To be checked, I have not tested.
-
1 point
Important Information
By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..