Eagle114th

Hello Stratos! It is great to see you here! I am not sure if you remember me, I posted at our forum we used to chill long, long time ago. It was C5 forum, along with Dave, Falc and other members. It is a great memories! So seeing you here brings me great joys! By the way, to answer your questions; I have not yet figured out how to edit the .dll nor .exe files of SF2 yet. I am still puzzled by it. From time to time, I take a look at the files using Ghidra. By the way, I planon sending you PM. Eagle114th

Hello everyone, After gong through manual and I realized that, the nature of CFS Type 97K is very dynamic with the gyro sight, moving veritcally depending on the mode and air to air combat situations. Unfortuantely, in SF2, it does not have dynamic sight mechanically. Therefore, I have no choice but to remain at 0 depression for gun. However, I moved the layout around to match the manual at zero depression for air to air. NOTE: This optical sight is for Mirage IIID / E / O with Cyrano II radar. The most interesting part about AG mode is that, according ot manual, for bomb attack, the gyro sight is depressed at 111.5 MILs. I tested it, turns out it does match the manual layout. However, for the rocket attack, it is depressed at 45 and it aligns with the rockets: And the reasons why I set it to 45 MILs depression, here ione page that talks about "EVELATION AND GRAVITY COIL": While the diagram in previous posts about G / R / M mode (Gun / Rockets / Missiles) set at zero depression, it stil have the capable of depressing from -5 to + 45 MILs., thherefore I set gyro sight to 45 maximum for rockets, which aligns with rockets as shown in screenshot. By the way, I am still workiong on adding the clourse speed for AA mode. However, I am still researching to see if I could add scale version. I posted the questions at this link: I plan on wokrong on earlier Cyrano I bis version for early Mirage III series, including Mirage III CJ "Shahak" series. Eagle114th

Found two fo very important pages for optical sight layout. I am re-working on the optical sight layout: Thank you Dtmdragon, while studying the sight you did for IAI Nesher, I noticed that the gyro sight is above the fixed sight, got me going through the manual again, then found these two pages! Just like I said, your files are a great help! Cheers!

I forgot to add one more notes about the color of opitcal sight. A freind of mine helped me researching and found a great video. Screenshot from video: (The optical sight cxan be seen from 11:00)

@dtmdragon Great information! I also have the information I would like to hsare with you too: I need the information for Israel Mirage IIICJ "Shahak" and IAI Nesher. they are great help for the projects! From what I have learned, it appear that Cyrano I bis and Cyrano II have some difference with the optical sight layout. It looks like Cyrano II have horizontal line (wings) which is used as roll tabs, linked to gyro sight, along with the closure speed scale. Cyrano I bis, in other hand, only have gyro sight, fixed sight, and hheading scale which also act as range scale. (As always, feel free to correct me if I am incorrect on any information). By the way, the optical sight I am working on is based on Mirage IIID and E, based on the information from Mirage IIIO - D flight manual. Here is information from the manual. If you want this manual, I can send it to you by PM.

Hello everyone! I have been working a lot on adjusting the minimum and maximum effective range of various guns for aircraft I have worked on so far in SF - CAP. Here is table I created as reference to help me figuring out the minimum and maximum effective range, as well the default range. NOTE: As stated before, the default range is usually 200 meters, unless the minimum effective range is above that, then that is used instead fo 200 meters. I wish that Thirdwire would have added dynamic gunsight (expanding / shrinking) because there is P-51 /F-51, as well F-100 and other that would have used it. Since SF2 does not have that, I choose 50 MILs as default size for these type of sights. Now that is completed, I am able to t move on to next aircraf.t I am currently working on Mirage III series. There are still more work to do. Here is CFS Type 97K sights: FIXED SIGHT GYRO SIGHT ROLL TAB (WINGS) HEADING SCALE SF2 screenshot (WIP - still have more to work on.) Eagle114th

Hello everyone! I have a question, I noticd that in Mirage III, thera are codes in cockpit: The isssues with this is that, it will always show up in all mode (NAV , AA, AG). I awnt it only displayed when in either NAV or AG mode. so ia m trying to implement the same type of heading via [HUD] method. Anyone know the methods to this? UPDATE: I have one more question, about this HUD symbol: Is there scale version of radar closurse vc? Thank you Eagle114th

I forgot to add, here is the updated information I have from researches on the MIGs and Js: (Thank you Stavka5 and Michaelk, and everyone for helping me with the information and data!) Eagle114th

>>> VIEW / CAMERA SYSTEM OVERHAUL <<< The works on AIRCRAFTOBJECT.INI allows me to edit the view / camera to give you more realistic feelings of flying aircraft. Based on the work of Warbirds's Realistic Head Movement base, modified it so the head movement is not as dramatic. Since in the early cold war aircraft to modern, the pilots are tightly melted on the chair, as well have Gs suits. Spent a lot of time testing and tweaking it. AIRCRAFTOBJECT.INIIf you don't have the file, here is the file. To install it, drop the file in Objects folder. Cheers!

Here is screenshot of MiG-19R / 19S / 19SV and J-6 / 6C / 6III Cockpit WHen switching to air to ground mode, the gunisght is in smaller size and is depressed for rockets and bombs MiG-19P / 19PM / 19PT and J-6A / 6B NOTE: - As stated above, the cockpit's radar lock light is re-positioned to align with the radar texture. ------------------------------------------------ >>> GUNASIGHT - 50 MILS GYRO SIGHT <<< This situation worries me because the gyro range, among aircraft are different and can cause us to miss targets when using gyro sights. Therefore, I started tweaking the Gyro sight based on 50 MILs. As stated, there is no dynamic expanding / shrinking gunsight for early cold aircraft, so all gyro sight is fixed as 50 MILs. First, I want to tell you what I learned about MILs size: MILs stands for milliradians. It is an angular measurement. 1 MILs = 1/1000th of the distance to the target. Simple formula for math: Size (in meters) = (Distance in meters × MILs) / 1000 With 50 MIls sight, at 100 meters distance (100 x 50) / 1000 = 5 Meters target size 50 MILs sight, 1000 Meters distance (1000 x 50) / 1000 = 50 Meters size However, there are various aircraft with different wingspan sizes. So it all comes down to what is most common targets that each aircraft faces or most likely. For example, F-86s, the most common target would be MiG-15, not Tu-95. Same with MIG-15, the most common or likely target would be F-86 rather than B-29. That is how I find the practical range for gyro sight based on aircraft and common / most likely target. Here is an example: for F-86's Mark 18 / A-1 / A-4 gunsight at 50 MILs and the wingspan of MiG-15 being 10 meters. Formula: Range = (wingspan of target x 1000) / MILs size Range = (10 m x 1000 m) / 50 = 200 m Therefore, the F-86F's 50 MILs gunsight would have default range of 200 meters. And for MiG-15's ASP-1N / 3N gunsight: NOTE: F-86F's wingspan is 11 M Range = (11 x 1000) / 50 = 220 meter Finally, there are three codes to look at from cockpit.ini: (For rangefinder / radar based gunsight) MinLeadRange= MaxLeadRange= (For non-rangefinder / radar or not using radar) DefaultLeadRange= After the projects with MIGs / Js are completed, I plan on re-visiting all of another aircraft's gyro range based on the data and flight manual.

Hello everyone! It have been a while since I posted here. There have been so much works done on the following projects: - MiG-9s / 15s / 17s / 19s - J-5s and J-6s (Will explain about J-2s and J-4s confusion below) - Cockpit tweaks / overhaul - View / Camera system tweaks - Gunsight and lead computing range for non-rangefinder, rangefinder, and radar version. ------------------------------------------------------------------ >>> CHINESE AIRCRAFT DESIGNATION SYSTEM <<< While working on both Soviet and Chinese MiGs and Js, I learned something very interesting about Chinese J series fighters history: NOTE: This is based on what I understand. If there is any information that appear incorrect, please post here and I am more than happy to discuss it with you here! I always learn new things everyday! Through deep researches, it turns out there are conflicting reports on aircraft names of Chinese La and MiGs aircraft imported by Soviet. According to the sources from China, there is no J-2 nor J-4, instead, there is only J-5 onward when they build aircraft locally for the first time, based on Soviet fighter aircraft. I have a theory why they chose number 5 for J-5 for Chinese version of Soviet MiG-17F, along with J-5A basing on MiG-17PF; For PLAAF (People's Liberation Army Air Force), China's air force starting in 1949, they have their own first fighter, which is imported La-9, followed by La-11 as second fighter. Then third, MIG-9s, then four, the MiG-15 and MiG-15bis. Then fifth being MiG-17 Fesco-A. Therefore J-5 (Mig-17F) and J-6A (MiG-17PF). Then there exists the J-6s (MiG-19). However, this get more interesting, initially they license built the copy version of MIG-19S, then they started evolving into their own built variants, such as J-6C, J-6III, and another variants, especially Q-5 "Fatan". By the way, there is also confusion with the difference between 'J" and "F', as well "Q' and A', and "H" and 'B". For aircraft that is locally built and used domestically by PLAAF is known as J, Q, and H series for fighter, attack, and bombers. When they export them, they become F, A, and B. Therefore, in SF2, using USERLIST.INI system for export Chinese aircraft as J-5s and J-6s is incorrect. They should be F-5s and F-6s. That is fixed in this SF-2 CAP next version, there will be two folders separately, one for PLAAF version and other for Export. For excellent works of Paulopanz's J-2, J-4, J-5, and J-6 packs, there is corrected names in SF2: J-2 -> MiG-15 Fagot-A, 1950 =CHINA= J-2 (51) -> MiG-15bis Fagot-B, 1951 =CHINA= J-4 -> MiG-17 Fresco-A, 1955 =CHINA= - ------------------------------------------------------------------ >>> MiGs and Js / Fs COCKPITS <<< The cockpit have been overhauled for radar texture, gunsight, position / offsets, and the trips on top of canopy. the gunsight have been re-worked as I find more information on them. Turns out that the radar symbol was too small, re-made that sight. There is also different size of sight for both AA and AG mode. In every aircraft, due to lacks of dynamic sight based on range for early cold aircraft (Expanding / Shrinking sights), al gun is always set on 50 MILs size by default, this includes MIGs and Js gunsight in this project. By the way, I would like to talk about the MiG-15s and 17s cockpits. After flying and testing various MIG-15s and 17s cockpit, I realize that it sometime feels like my head is too close to the reflector glass, so I moved back while ensuring that the S-13 (fixed sight of ASP-3N and ASPP-4N) still fits the reflector glass. so here is updated cockpit view: MiG-15 MiG-15bis MiG-17 / 17F / J-5 MiG-17PF / PFU / J-5A NOTE: - here are EARLY and LATE version with RP-1 / P-1 and RP-5 / SL-1. RP-1 and RP-2U have orange radar screen with track range of 2 KM while RP-5 / SL-1 have tracking range of 4 KM. - Stary's great works of MiG-17FP / FPU cockpit have radar lock light. While being unable to re-size it, it is moved to align with the texture of RP-1 / P-1 and RP-5 / SL-1. - The radar hood have been tilted toward the position of pilot, for better visibility of the radar scope and the instruments. >>> Operating RP-1 / P-1, RP-2U, and RP-5 / SL-1<<< From what I have learned, the radar have two mode: Search and track, whichi s very simple. So in order to track, you can switch from search to boresight mode. And please note that RP-1 and PR-2U have track range of 2 KM while RP-5 have range of 4 KM. All share the same range of searching around 12 KM. Search mode for RP-1 / P-1 / RP-2U (When the target pass the 2 KM line, that is when you can to switch to boresight to track the target) Here is TW style version of RP-1 / P-1 and RP-2U RP-5 / SL-1 radar in MiG-19FPU (1957)

Hello everyone! Thank you for the replies! I think I will do a ful re-installatino of SF2. it have been many, many years and several of former HDD and SSDs transfer. It's time to do reinstallatino of SF2 while preserving the mods folders. Just recently, I upgraded 1 TB SSD to 2 TB. But this one is a bit pain in ass, so I am investing into next newer external SSD. (For now, i am trying to torubleshoot the issues with new exteranl SSD, it kept staling in aninterval when saving projects fo editing images or text files. I amusing ScanDisk nvme ssd extreme by the way). At least Ihave one solid old SSD (1 TB) that I have all copies of SF2 files in safe place, along with the library. Cheers!

Yes, it is for visual, by pressing T to have red square appearing on that target and padlocking it. When encountering F-86D, I could pres T and red box appear, then apdlock for a moment or so, then suddnely become unselectable (pressing T no longer work) and it onlya llow me to padlock on another target instead of that F-86Ds. It is a strange situation. Eagle114th

Hello everyone, I am currently workinog on J-2s / 5s / 6s and while testing them, I face F-86Ds during recon mission, I went into defensive tactic against them and they suddenly disappear from being sselectable target visually. I could no longer press T to have red square apeparing on taht F-86D to padlock them. I can only select another target besides F-86Ds. By switching to an external views to next aircraft, and I could see F-86D still flying. This puzzles me for a while and I am constanlty going through F-86Ds made by Wrench and Yak79. Going through the F-86D's data file, I noticed taht the [AIData] is missing is it required, inorder, for aircraft to remain being sellectable when encountering enemy aircraft? Here is data files from one of F-86Ds: F-86D-45_DATA.ini It is my goal to fix this, so any aircraft that is ecoutnered, does not suddenly become unselectable as target.

I just realized that you were talking about MiG-19s when I thought it was MiG-17. I apologize for my confusion. It is my fault. Now I understand, here is thelist you have provided: Eagle114th