DoctorK

OK, I see what you mean now. Well, at larger delta H, 1 click angle increment will be smaller. This means you will have more overlap when scanning the extremes. So you don't have to worry about the gaps.

You don't need any complicated math to move the scan zone. You only have to look closer to the scan coverage bar on the HUD. Note the bar length represents the vertical scan coverage, 10 degrees. In this example, you can read the scan elevation coverage is from about 20 to 30 degrees and the HUD view coverage is from about -7 to 13 degrees. Yes, the radar is scanning the area above the HUD. When you move the elevation angle to scan broader volume, memorize the last bar coverage first, then increase/decrease the height offset so that the new coverage has some overlap with the last coverage. By this method, you can scan broader volume easily and efficiently without any gaps.

EDIT: Sorry, I was wrong. I assumed it was unfixed like many other bugs of HSI, AOA gauge, Flight director in HUD, Backup speed meter...

Kuky is right. Looks like the cdds name in graphics.cfg is missing. Reinstall the mod again, or add the cdds name manually. The red line is needed in Config\graphics.cfg. And you don't need Aero's textures to see my mod. Those are not part of my mod, just a expansion.

It's my mod without Aero's mod mixed.

The one big restriction of the lighting is the needle color which is hard coded and can not be changed. So, I chose the needle color as the mod's light color. It's less orange than the original and the gauges match perfectly to the needles. I also changed the way of textureing. Whereas the original replaces the lit parts with the night textures, my mod adds the highlights only. By this change, the color looks more natural at various situations. You can see it in these examples. Original Mod Original Mod

Maybe you guys don't know there are some additional files for Aero's mod posted here. http://forums.eagle.ru/showpost.php?p=868353&postcount=53 I should have said my mod + Aero's Modman pack + Aero's additional files + AeroUpgrade is what you want.:doh:

You have to install Aero's mod, too. My mod + Aero's mod + AeroUpgrade is what you want.

Oh well... Forget everything, and put the TGAs in the attached zip into Temptextures folder. I fixed the files for you. AeroUpgrade.zip

No. You want to change Aero's BMPs to TGAs.

I think Aero is working on it right now. Anyway, you have to change the texture names and types. Follow the list of changes shown below. And, when you change BMPs to TGAs, do not forget adding an alpha channel first. F-15-CDU.bmp > F-15-CDU.tga F-15-FUEL.bmp > F-15-FUEL.tga F-15-HUD-CONTR.bmp > F-15-HUD-CONTR.tga F-15-MPCD-DISPL.bmp > F-15-MPCD-DISPL.tga F-15-RADAR.bmp > F-15-RADAR.tga F-15-SPEED.bmp > F-15-SPEED.tga F-15-TEWS.bmp > F-15-TEWS.tga

The real HUD does look like these. Yes, it's beveled. But you still see the upper surface because of the light refractions. See this diagram. I changed the texture names and types to isolate the shared files and/or add the alpha channel. I masked out the part of the rail over the indicator to reveal it. Here is the complete list of changes. This is described in the mod readme, too. A-10-ALT-PLASHKA.bmp > F-15-ALT-PLASHKA.bmp A-10-ALT-PLASHKA-N.bmp > F-15-ALT-PLASHKA-N.bmp A-10-ALT-PLASHKA-TEN.bmp > F-15-ALT-PLASHKA-TEN.bmp A-10-ALT-PLASHKA-TEN-N.bmp > F-15-ALT-PLASHKA-TEN-N.bmp A-10-RUCHKA.tga > F-15-EMG-OPEN.tga F-15-CDU.bmp > F-15-CDU.tga F-15-FUEL.bmp > F-15-FUEL.tga F-15-HUD-CONTR.bmp > F-15-HUD-CONTR.tga F-15-INSTR-11.bmp > F-15-BKUP-GYRO.bmp F-15-INSTR-11N.bmp > F-15-BKUP-GYRO-N.bmp F-15-KNOPKI.tga > F-15-HSI-RING.tga F-15-KNOPKI-N.tga > F-15-HSI-RING-N.tga F-15-MPCD-DISPL.bmp > F-15-MPCD-DISPL.tga F-15-PRIBORY-2.bmp > F-15-PRIBORY-2.tga F-15-PRIBORY-8.bmp > F-15-HUD-FRAME.tga F-15-GLASS.tga > F-15-HUD-EDGE.tga F-15-PEREPLET.bmp > F-15-PEREPLET.tga F-15-RADAR.bmp > F-15-RADAR.tga F-15-SPEED.bmp > F-15-SPEED.tga F-15-TEWS.bmp > F-15-TEWS.tga ILS-REFLECTION.tga > F-15-HUD-GLASS.tga KOMPAS-PLASHKA-MIG.bmp > F-15-COMPASS.bmp KOMPAS-PLASHKA-MIG-N.bmp > F-15-COMPASS-N.bmp ZERRKALA-BLIK.tga > F-15-MIRROR.tga

I brighten the rail a bit. See the first post. The collaboration is welcome. You can combine my work with yours.

F-15C Cockpit Upgrade for FC2 and 1.1 EDIT: Slightly brighter version 1.01 is available. Visual Upgrades: - New HUD - New Canopy Frame - New Mirrors - New Gauge Light Color - Improved HUD Control Panel Outline and small refinements everywhere. Functional Upgrades: - Fully Visible Annunciator Panel - Corrected ADI Waterline - Recalibrated Speed Meter ModMan compatible. Normal Version; http://www.lockonfiles.com/modules.php?name=Downloads&d_op=viewdownloaddetails&cid=269&lid=1772&title=F-15C%20Cockpit%20Upgrade#dldetails http://www.filefactory.com/file/b1cdb43/n/F-15CockpitUpgrade101.zip Fake Mirror Version for those who don't use mirrors; See the second image attached. http://www.lockonfiles.com/modules.php?name=Downloads&d_op=viewdownloaddetails&cid=269&lid=1773&title=F-15C%20Cockpit%20Upgrade%20with%20Fake%20Mirrors#dldetails http://www.filefactory.com/file/b1cde7c/n/F-15CockpitUpgrade101FakeMirrors_zip

The black line problem is due to how the pixels are interpolated at the texture edges. The opposite edge pixels of the texture will be used as the 'neighbor' pixels. I attached a alpha channel comparison between the original and Ricardo's texture. In the original, you can see some narrow black area at the right and the bottom edge to prevent the black line. So, Richardo can do the same to solve the problem. I also attached a temporary fix as a zip file. Place the unzipped tga in Bazar\TempTextures. Don't forget removing the file when Ricardo has released the new version. PRIBORY-09-27.zip

The slew speed is related to your frame rate. So, you can slow down it by limiting the max frame rate. Open \Config¥graphics.cfg and change MaxFPS from 0 to a certain value, say, 30.

Version 1.04 is available. Now, you can set Lock on path manually. http://www.filefactory.com/file/a2d1396/n/RaMGen104.zip

Hi, The problem happens when you moved Lockon files from the installed location. Ramgen tries to find those files at the location described in the registries which can not reflect the move. So, you can update the registries to solve it. The key is "Path" in "HKEY_CURRENT_USER\Software\Eagle Dynamics\Lock On 1.1" Please edit it to the current path. Sorry for your inconvenience.

Looks like they updated the afterburner flame.

Yes. You can see it in this FC2 video. http://forums.eagle.ru/showthread.php?t=47242

I noticed two new features. 1. HUD letters are half transparent. 2. The player can roll the view in the cockpit. Very nice.

AI planes do not use external fuel. This is a bug. You can confirm this by comparing the AI's flight time on a looped path with and without external fuel tanks. In ModMan, you can set the game path manually in the options. Click the button at the upper right corner.

I heard the next patch is coming, so I wrote down all issues I can remember right now. I hope these are fixed. EARLY WARNING RADAR: - EW radar detects all aircraft at same range no matter what size they are. AWACS: - AWACS tells "Hot" or "Cold" based on the bandit's closure rate. This should be based on its heading. US AIRCRAFT: - The heading bug on the HUD shows wrong direction when there is north direction between the aircraft heading and the waypoint direction. - The actual gun rate does not change between high and low gun rate mode. The rate is always high. A-10: - Maverick missiles can hit the targets only when the missile effectiveness is 50 or 100 %. - VSI indicater on the HUD does not show its scale when the scale is "1". (This may not be a bug.) F-15: - HSI does not work in AA mode. - IFF system does not work in STT mode. - Post Launch Timer shows unknown numbers after the AR missile has gone active in TWS mode. - HOJ lock can be detected by the target aircraft. - True speed indicater in VSD shows IAS. - AOA indicator shows its value not in units but in degrees. - Backup airspeed scale shows wrong number. AI AIRCRAFT: - AI aircraft do not use external fuel. - SEAD aircraft try to destroy non-radar vehicles in the assigned target group. - AI aircraft try to attack detected enemy air defences first no matter what task or target they are assigned or weapon types they have. This happens even when the enemy air defences are very far away compared to the assigned target. CRUISE MISSILE: - Ship-based cruise missiles can not been launched when there is terrain obstacles between the target and the ship. RWR: - RWR does not detect friendly ground-based radars. MISSION: - When the mission date is 2 or later, the cockpit illumination is always lit at mission start even in daytime. - When the mission task is SEAD and the target group includes non-radar vehicles, all target vehicles must be destroyed to get 100% achievement. PILOT LOG BOOK: - When the mission date is 2 or later, the "TakeOff" time in the mission log shows the number which is larger than 24:00.

In your lockon-doc folder, there is another pdf named QuickStart-something. You can find some mission editor descriptions in it.

Version 1.03 is available now. No big changes, only small corrections. http://www.lockonfiles.com/modules.php?name=Downloads&d_op=viewdownloaddetails&cid=188&lid=1367&title=RaMGen:%20Random%20Mission%20Generator%201.03%20for%20LOFC#dldetails or http://www.filefactory.com/file/af3f8df/n/RaMGen103_zip You can replace only "RaMGen.exe" to upgrade. Version 1.03 - A decimal separator problem on certain Windows localizations solved. - Russian version of Flaming Cliffs supported. - "Name" button to switch weapon names between the original and the modified ones.