orsin

I have always prefer the stock TW A-6 cockpit than Razbam one. In fact it is one of the high quality pit back in Gen1. So sad there is no stock Intruder in Gen2. It could have been one of our favourite. The stock pit has only one display working which shows the radar. Over the years there doesn;t seem to be much exploration of TW stock A-6 cockpit on the forum. So I tried and modified a bit... In reality, it can be pretty informative now a days. There is no point to argue the accuracy of historical pit. the radar is placed at VDI location at the first place.

Gents this is an experimental effect in the works. I wonder anyone have tried use effect in cities to create constant light visible at night in the past. I have some quick try and managed to generate 10 simultaneous light source per attached object, however the effect looks really pathetic. Has anyone go any idea how to avoid the terrain being "overexposed"??

It probably means then we need to update the stars.DAT file, however this then requires all tod coordinates of all maps to be updated to it. I tried introduce the shader FX for stars to the solidobject buildings however no difference made.

no this is not based on fake base. Totally irrelevant.

It actually look very presentable when look far But Once you get closer ewww By reducing the light range I can have less artifacts, but it then requires more source as those are constant emiters and they compete resource with other effects like rain etc. I was thinking of adjusting the render part of the effect but so far no clue? Any help?

Some time ago there was mig-25PD in the work, then it disappeared. Has anyone received the MAX file or beta version?

Is it still to see the light of day some near future¿

File Name: Heavy Rain File Submitter: orsin File Submitted: 30 March 2016 File Category: Environmental Mods This is a re-re-mod of Stary's rainstorm weather http://combatace.com/files/file/10945-thunderstorm-weather-mod-experimental/ and BearGryllis' TPWEL : Thunderstorm Pack With Enhanced Lightnings 2.0b http://combatace.com/files/file/12793-tpwel-thunderstorm-pack-with-enhanced-lightnings/ Hats off for their contribution to the community. It is an extraction of a much larger overall mod that has gone for years internal of our team. It is considered stable enough and deserve for a release up to date. The goal of this mod is to create an improved rain scene for SF2 titles. We have changed the 2 earlier mods on below field. 1. straight rainfall with speed, no longer slashed 2. removed the abnormal light surrounding aircraft on the ground when take off 3. reduced much on particle consumption to have a bit more consistency on presence. Less chance to have rain stopped when explosion happened on ground. 4. When speed pick up, the rain is less visible to represent reality. Installation: Drop everything in "Effects" folder. Click here to download this file

Lately I noticed my SF2NA doesn't start properly at times. It appears that the game has started, and I can hear the radio conversation, or even turn on auto pilot. However the SCREEN is still stuck at 80-90% loading and never turn to the actual game scene. After nearly 10 hours drilling down the cause, it turn out to be the Mirage F1C series. Whenever the game take them as battle aircraft or parked aircraft, the problem occurs. Strangely this only occurs on certain maps, modded Genmany (Rend's), modded Israel (Stary) and stock Iceland. F1C is the only plane that I found caused the problem. Occasionally the game loads to the runway, but all planes are placed in the center of the runway and blast into fireballs. Any thoughts?

This problem has been concluded to the 4096 x 4096 BMPs and JPGs used in Mirage F-1C. Somehow the game engine or the video driver doesn't like it. The more planes in the game the less the stability. When it goes beyond a certain quantity, the game starts without the 3D world initialized. While the modern video cards can handle textures of large size with no problem, it seems suspicious that somewhere in the game engine there is a limit. Reduction of the texture size to 2048 is a great boost of stability.

View File Mi-24P Public Beta Please note: The default Flight Model is designed for "Hard" setting only, and takes off vertically. If you are using "Normal" or "Easy" settings there is no guarantee that it would work. Use "H" Key to switch between front and back seats Package has included an optional flight model from Marcfighter for try out. Mi-24P public beta proudly present to you by YEYEYE. This is a highly detailed model with proper cockpits and LOD files. This model has no relevance to A-team's work. Model/FM/Weapon/Cockpit - YEYEYE FM and beta test - Honeyfox, Orsin Optional FM: Marcfighter, Floran Commercial use of Mi-24P and all its parts are strictly prohibited. All rights reserved. This is a public beta released as-is, please use on your own discretion. The authors and CombatAce do not take any responsibility should damages occur to your property. Modifications/Improvements to the Data/INI/Texture are all welcome. No consent from the author required. Submitter orsin Submitted 04/29/2012 Category Mi-24  

For that beloved Fulcrum... This is my first attempt of so called "cockpit detailing"...

Woola! This is a long waited pit and a significant boost for TMF Mirage F1. The original one is OK but bit dated. The weapon selection panel is much more accurate than the original one. We refered to the french operation manual and check one by one..

I have noticed a messaging system problem. Whenever your PM contains a HTML link within, the sent message will be truncated to the end of this link. Any further letters will not be sent thru. You will have to go to message box and manually revise it. Can someone have a look?

Just manage to reproduce the problem. see your PM

Well, to explain this you need to understand what DVI and PHD does DVI basically looks similar to F-14, serve as a ADI like device when radar is not performing. However that is just a simple implementation. Its main function as a output of the DIANE system displays some horizontal view of ground profile. According to materials I found, if there is a "V" shape valley in front of nose, DVI displays bright image on left and right, and dark image in the middle. This implementation is similar to terrain avoidance mode. PHD on the other hand displays the digital HSI needle like F-14 when radar is not performing. Its main function as a output of DIANE is to plot vertical profile. If in front of nose is a uphill, the PHD plots the ground shape like a up graph like this https://encrypted-tbn2.gstatic.com/images?q=tbn:ANd9GcT3R9XE5rTnNUUxjenUH0yCGDwpdJtzBph3iw--r_oTKD30KvVZ_Q where the left-most part of screen indicates the location of the plane. This can be mimic by putting a camera external and far to the aircraft. The camera looks at A-6A from right hand side. However to accomplish this, the PHD must be able to display radar/TV first - Which is not achievable now due to the lod. Not to mention TV and Radar cannot function simutaneously at the moment

Well, A-6A calls for some SFP1 stock textures. ACCELEROMETER.BMP ALTIMETER.BMP CLOCK.BMP F-8E_PIT1.BMP FUEL_QUALITY.BMP GAUGES15.BMP INTERGRATED_POSITON_INDICATOR.BMP RATE_OF_CLIMB_INDICATOR.BMP HUDGLASS.TGA HUDGLASSTOP.TGA HUDREFLECTION.TGA

Stop day dreaming. That is hopeless... A least simulated A-6A would require TK to vanilla F14.dll and avionics60.dll together. For a DLC that is not going to happen. Not to mention the VDI and PHD displays are so much more sophisticated than just dark green dots for the ground and white clouds for the sky.

no. needle's y axis is at the centre of triangle. so not usable after all.

well found the answer Another feature in the A was Elevation Scan (E-scan). With E-scan the A's AN/APQ-112 track radar was used to generate vertical terrain development on the Pilot's Horizontal Display (PHD) the CRT immediately below the VDI on the pilot's side. The pilot read vertical development "left to right" on the PHD, with obstructions closer to the aircraft appearing on the left side of the PHD and those at greater range lying more to the right. (Again, I apologize. This is hard to describe without a graphic.) E-scan return would gradually slide from right side of the display (farther away) to the left (closer) as the flight progressed and new return for the same terrain was processed. The information displayed on the PHD in E-scan also included a flight path line and a clearance line. The pilot would scan both the VDI and the PHD while flying in E-scan mode, performing the necessary spatial interpretation gymnastics to deduce how close the A was to a possible prang. It is not something we can get anywhere close with TW's code. So I'd happy just leave it as a map display