OlWilly

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

On 08.08.2023 at 8:10 PM, one4five said:

no INI edits though?

like detection FOV or something similar

i come in tree top, hide in the hills or behind a ridge, turn/climb 6oclock, as i get into 2 miles away the SOB jinks hard! like WTH! 

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

On 5/14/2023 at 9:17 AM, michaelk said:

Try to ask the cockpit authors a question (mr. Stary etc), including about the features of the work of the red side RVR's.
At least I left everything as it is on my 23x (maybe just delete the second PVR/SPO later).

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

5 hours ago, GKABS said:

But do you believe that they hit target from 1000 Kilometers with accuracy??? 

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

2 hours ago, bazillius said:

When i say "Painful" i mean everyday desturbing my sleeping. Effecrivness of Iranian drones is zero. Only mental. You wake up not fresh. I think thhese cruise missiles arethe same shit. Shahed - 136 , Grad Partizan etc the weapon of civilian terror, not the weapon in classic meanin. The target of this shit is not point, is not wehicle is not electrick station. The targrt is town itsels.  Its like a bomb with nails in the underground station. Psychological effect but not military casulties. They are vert annoing but thats not gamechanging weapon. The same with all other missiles i have seen.

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  

17 hours ago, bazillius said:

Their drones are painful. You know that i know that. But i still havent seen balistic missiles from Iran

New cruise missile from Iran -

13 hours ago, bazillius said:

Delete your Iranian version of Su-35 in a trashcan (Joke ! Thats the nice skin!) They can lie. Or it isanother reason: Russia is not capable of making the Su-35 amymore. A few years ago I was surprised that Egypt bought the MiG-29M2 (2017 if i remember right). For what? Why? who will serve them?  They would ask me, and I would advise them to buy ... Whatever they sell, then buy instead of Russian aircraft. We will not see Russian weapons anymore.

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

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 

1 hour ago, FLOGGER23 said:

So, I invite you to join the painstaking world of modding my friend, and help us have more toys to play with...

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.

37 minutes ago, Stratos said:

Not according to me, but according to TK, the thing is CA do not want to get involved, and I respect that.

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 

On 16.07.2023 at 5:27 AM, bazillius said:

Pity we have no script and compiler to edit and mix avionic dlls

It is possible, but requires someone with extensive knowledge of dll libraries.

Also I recon the administration of the site doesn't want such things as they will annoy SF developer. So if this happens, someone has to host modified files away from Combatace

On 15.07.2023 at 7:43 PM, simonmiller416 said:

If I was flying a multirole fighter like the F-35 or F-18, I wouldn't be willing to make compromises

In the environment of SF2 engine, TWS mode is more important than ground mapping feature.

Ground mapping is mostly for eye candy while TWS allows the proper use of missiles like AMRAAM, R-77, R-37 or Meteor. It makes no sense flying something modern if you still have to guide AMRAAM like a Sparrow

If you still want to retain ground mapping feature, it makes sense to do two aircraft versions: one with 70.dll for strike missions, other with F-14.dll for air-combat

On 16.07.2023 at 10:08 AM, Menrva said:

If the plane and cockpit can be released with due credits to the authors, I'd be happy to include this new Su-24 in the ODS 30AE mod as a flyable aircraft.

While we're at it, I have a question.

I noticed that ODS has a dedicated MiG-25 cockpit which is not available for separate download.

I took a gander at it, found some things that warrant fixing.

For a time, it's for my personal use. But if you/creators don't mind, I can upload the fixed version after I finish it. Or pass it to you for ODS update

A dedicated Su-24 cockpit?

Share it guys! It's a crime to keep this beauty away from the people.

I also already see lots of typos in the labels, may fix them for release

I have other pits in the work for the time, but they will wait

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?

On 06.06.2023 at 6:08 PM, Righteous26 said:

Some aircraft such as certain A-4 and A-7 variants have this. Look for a small green light that reads "IN RANGE" or something similar.

Yes, found it - "weapon shoot cue"

I had the impression that it is not working properly but it does. The problem is in each missile data file, some of them have seeker and launch ranges different, thus the node can give you "launch authorized" signal when the ranges is met, but seeker has not locked on yet.

Sadly, this doesn't seem to work for guided bombs, so it's better to enable CCIP for guided bomb runs