OlWilly

More stuff for MiG-21 This scale right below the gunsight is actually a radar range indicator. Lowest part shows the distance to the ground in ground attack mode (not applicable in SF2), the one above it shows distance to aerial target in air-to-air mode. Very useful thing, allows you to know the range for sure and pick the best time for a launch To enable, replace original AgujaBB entry by this: [AgujaBB] Type=RADAR_TARGET_RANGE NodeName=AgujaBB MovementType=ROTATION_Z ValueUnit=METERS Scale=1 Set[01].Position=-20.0 Set[01].Value=1000.0 Set[02].Position=20.0 Set[02].Value=9000.0 Sadly, this scale is properly animated only in these MiG-21 pits. In his works, Stary just put it as a solid texture with arrow being painted on it 3km:

I noticed that MiG-21MF pit has working Bereza RWR. It bleeps and lights do show the angle of incoming radiation MiG-23 pit has Bereza too, and it looks like a same 3D model, but currently lights don't work. It bleeps, but no lights Another thing, 21 pit has "droptanks empty" indicator light. Very useful. 23 pit doesn't Thus, how exactly I can edit 23 pit to add this? I understand that I had to modify 3d model of the pit, add hooks and respective light textures, then add them in cockpit.ini having 21 pit as an example. What software is best to use here?

View File Su-35S cockpit by Insky, light update A light overhaul of old Su-35S cockpit by Insky. Sadly, it is of lower fidelity than Su-27SKM cockpit from YeYeYe which is often used for modern Su-27 derivatives, but it follows the general layout of Su-35S cockpit and is worth a try. Updated textures, sorted out various indication and HUD, some other small fixes. It is tailored for Su-35S by GKAB, but could be adapted for any other aircraft. Caution: there is no "launch authorized" indication on the HUD, not possible to add it with resources I have - it will be displayed on the radar. Real Su-35 pipes both radar and RWR information straight to the HUD, which is not possible to recreate in SF2 engine - so we have what we have. To install, delete original files in Su-35 folder and put new ones inside Submitter OlWilly Submitted 09/06/2023 Category Jet Cockpits  

Size for MiG-21MF is different: SearchPosition=0.6 TrackPosition=0.6 LockPosition=0.6 SearchSize=0.9 TrackSize=0.9 LockSize=0.9 Although I removed additional lights, leaving only four (as it should be). Comes with adapted texture Instrumentos05.tga Same set-up for Su-15 pit, and changed texture instruments.TGA

Only if it happens, eye candy will be improved, but functionality will get closer to ace combat series Not sure if anyone wants it

Missile approach warning is a standard since original Su-27

Well, took me a while to figure it out properly The set-up has two nodes. Outer node is basically for decoration (or, so to say, to imitate the actual SPO-10), in Stary's cockpits it's usually called "RWR_front". This node calls TGA texture, and it is in TGA format to allow transparency. The holes are placed where the lights should be. Better seen on a screenshot in the post from May. The actual RWR node is the hidden node inside (here, called simply "RWR"). It calls BMP or JPG texture, and it should look the same as the outer texture. All of this is already done in the cockpit model, no changes to textures are necessary so I just explain how it works. Thus, in cockpit ini: [RWR] Type=RWR NodeName=RWR In avionics ini: [RWR] Type=3_RING AirSearchTexture=cockpit\rwrGreen.tga AirTrackTexture=cockpit\rwrYellow.tga AirLockTexture=cockpit\rwrRed.tga GroundSearchTexture=cockpit\rwrGreen.tga GroundTrackTexture=cockpit\rwrYellow.tga GroundLockTexture=cockpit\rwrRed.tga SearchPosition=0.60 TrackPosition=0.60 LockPosition=0.60 SearchSize=0.7 TrackSize=0.7 LockSize=0.7 SearchFlash=FALSE TrackFlash=TRUE TrackFlashRate=0.5 LockFlash=TRUE LockFlashRate=0.1 ShowSearchRadar=FALSE TrackSound=MiGRWRS.wav LockSound=MiGRWRL.wav This way, the RWR node works just as a regular 3_ring RWR, showing the general direction of the radiation. The goal is to find proper position so the light will align with aforementioned holes and will be seen outside. Position=0.60 works fine Then, the size should be adjusted so the lights are big enough to be seen from outside - if you make them too small you won't see anything most of the time. Size=0.7 works fine I did increase the number of transparent holes on TGA texture from 4 to 8 for testing, but it is not necessary - the actual SPO-10 had only four (this is where Stary pit is correct and MiG-21 version is not.), so I returned them back. As a bit of trivia, the actual SPO-10 worked in a way that: - the lights show you the direction of radiation, white color only - the frequency of beeping tells you how close the threat is (faster beeping - closer threat) - continuous beeping means you are locked - not sure for what purpose the red lights are, either range or launch warning Most of this is not possible inside the game's engine, so we multicolored RWR would be good enough. TLDR - just check the correct paths and names for all textures, Position=0.60 and Size=0.7

AFAIK, "detection" section of each DATA.ini file has something about visual radius and deadzones. It's in the beginning of the file

I finally made it work

I occasionally ran out of fuel and either glide back to the nearest airfield or land right on some field. Game doesn't simulate bumpy ground regardless, so should be a loss or crash-land. Crash landings are not simulated too, right? You just explode Never seen AI running out of fuel though

Why not? GNSS really changed a lot. Back then accuracy sucked because of imprecise INS navigation and limited radar ground lock capabilities on such missiles (missiles like Kh-22 are notorious for having a massive CEP) With GNSS, 25m CEP at any ranges is just easy

Shaheds could definitely hit their targets. Reni port: …faceofwar/32682 SBU headquarters: …faceofwar/31977 Ammo depot: …faceofwar/32548 And so on. And they are fairly hard to intercept while being dirt cheap. Although those are Russian Geran-2 drones which are derived from Shahed-136 but have some local changes. I think Saudis should start getting nervous right now. If Iran gives enough Shaheds to Yemenis, they could literally cripple Saudi oil production and ruin their economy. Imagine Abqaiq–Khurais strike but on country wide scale

New cruise missile from Iran -

Su-35 are still produced like before. The last batch was in July: Iran's reluctance to buy more Su-35s comes from the really stupid statement of Russian diplomats: https://www.aljazeera.com/news/2023/7/12/iran-summons-russian-envoy-over-statement-with-gcc-on-islands

View File MiG-25 cockpit fixes (actual MiG-25 cockpit by Centurion-1) MiG-25PD cockpit by Centurion-1 with fixes Notable fixes include: - removed gunsight. 25 doesn't really need it, most of the footage shows 25s without gunsight - fixed G-meter: added negative Gs and redid the layout to be more in line with the real thing - original model actually had airspeed indicator and altimeter confused - this was corrected. Altimeter is above (shorter needle shows thousands, longer hundreds, plus analogue counter), airspeed indicator is below (likewise - shorter needle shows thousands, longer hundreds) - fixed vertical velocity indicator. It wasn't working due to "values" being put in the wrong order (could be that it was working on older patches) - fixed compass and course arrow. They were calling non-existing nodes - added over-G and too much AoA lights above G-meter: not sure if realistic, but will do - added afterburner light near nozzle indicator - removed some lights and switch animations: they are cute, but very incorrect - MiG-25PD version gets new radar layout taken from MiG-23 radar: it makes sense as PD radar "Sapphire-25" was developed from "Sapphire-23" on MiG-23 - can't do anything about warning lights and gear/flaps indicators not working - cockpit model just lacks any light nodes - added some labels on instruments --------------- Install: remove old cockpit folder, *cockpit and *avionics files, drop in new ones, rename accordingly. Cockpit versions: 25P - for MiG-25P 25PD - for MiG-25PD/PDS 25PD uses avionics70 dll! Make sure to address it in the init file: AvionicsDLL=Avionics70.dll 25PD is tuned for MiG-25PD from Coyote Airspace. It is easily adaptable for older versions of PD/PDS, just change position values in *cockpit file. Submitter OlWilly Submitted 07/19/2023 Category Jet Cockpits  

I uploaded a new version of Su-17 cockpit pack, it is still not approved. Is there something wrong with it or you guys just don't have time?

Sorry for bothering you guys - but some things just keep getting stuck on my mind. Looking at my download page for this: https://combatace.com/files/file/17961-mig-23-cockpit-fixes I made a really messy download page, didn't even put readme inside, and installations instructions are sketchy So I got to put it in more orderly way

Sure. If I will still be around when the package will be getting ready for release, pass me cockpits for checking. YEYEYE makes great cockpits, but usually with lots of misspellings in Russian labels, plus some instrumentation may be wrong due to translations issues

I understand your considerations and all... but you had ready quality cockpit for Su-24 and just kept it away for 7 years? This is the only Soviet two seater cockpit that I have ever seen on this site. Aside from Su-24 it could be used as stand-in for Tu-22M and Tu-160 as they still use American cabins.

This is what I say - if anyone ever does such a thing, the new files should be hosted away from Combatace. Preferably by someone from another country

I dropped YEYEYE the message... but his profile says that he wasn't around for two years. If anyone knows his e-mail one can send him a message too