orsin

Does any one know if it is possible to assign an overlay texture to a TV display when it is OFF? I'm trying to create a dedicated TV screen for A-6 series cockpit. While there are limited nodes to play around. I need to get a texture mask displayed even when TV is off. Is there a way?

Here is the "out" file Anything double slashed have been used by the stock INI. //---------------------AOA //angle_of_attack_indicator //needle_angle_of_attack //--------------------radar altimeter //radar_altimeter //needle_radar_altimeter //radar_altimeter_knob //--------------------tachometer //tachometer_exhaust_temperature //needle_rpm1 //needle_rpm2 //--------------------exhaust gas temperature //needle_egt1 //needle_egt2 //--------------------fuel flow indicator //needle_ff1 //needle_ff2 //--------------------radar screen --------------------------------- //vdi_component //vdi_component_lens //!!!!!!!!!!!!!!!!!!!!!!!!!!!! next to radar lights, not used yet, has texture to "light up" !!!!!!!!!!!!!!!!!!!!!!!! Vdi_Button_in range Vdi_Button_computer Vdi_Button_Attack Vdi_Button_Plateform (this is not typo, it is what it is in lod) //---------------------altimeter //Altimeter //needle_altimeter //altimeter_dig1 //altimeter_dig2 //altimeter_dig3 knob3 (not sure used or not) //--------------------gmeter //g-meter //needle_gmeter //!!!!!!!!!!!!!!!!!!!!!!!!!!!!not used yet!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! hook_lift/gyro_fast_erect_panel vertical_gyro_indicator vertical_gyro_indicator_knob //--------------------ADI ball //ADI sphere //!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!ACLS next to hud, not used yet, need needles!!!!!!!!!!!! acls_indicator Acls_lens //--------------------HSI //horizontal_situation_indicator //horizontal_situation_indicator_knob_a //horizontal_situation_indicator_knob_b //HSIwheel //HSI_center //HSI_CourseDeviation //HSI_CourseArrow //HSI_HeadingMarker //HSI_pointer //HSI_plane //HSI_rangedig1 //HSI_rangedig2 //HSI_rangedig3 //HSI_coursedig1 //HSI_coursedig2 //HSI_coursedig3 //!!!!!!!!!!!!!!!!!!!!!!!not used yet!!!!!!!!!!!! oxygen_quantity_gauge_A needle_oxygen_quantity_gauge //-----------------------clock //clock //needle_clock02 //needle_clock01 //needle_clock03 (??? one of the 3 needle is in wrong place??? hovering next to clock) knob1 (not sure if used) //----------------------rate of climb //rate_of_climb_indicator //needle_rate_of_climb //---------------------TURN INDICATOR //md-1_turn_and_slip_indicator //turnsphere //needle_turn //--------------------another part of ADI //ADI_watermark //ADI_BankIndicator //bracket //!!!!!!!!!!!!!!!not used!!!!!!!!!!!!!!!!!!!!!!!! metal_plate metal_tube //------------------Indexer left to hud //approach_indexer02 //indexer_slowL //indexer_on_speedL //indexer_fastL //------------------right to hud //approach_indexer //indexer_slowR //indexer_on_speedR //indexer_fastR //----------------------machmeter //gauge_machmeter //machmeter_wheel_right //machmeter_needle_speed //machmeter_needle_small //machmeter_speedwheel //machmeter_machscale //---------------hud //optical_sight //optical_sight_glass_lg //optical_sight_knob ???????????????? //HUDend //optical_sight_glass //-----------------standby Compass---------------- //standby compass //stby_comp //stby_comp_darkbox //---------------------cockpit walls and glasses, no use housing_a pilot_instrument_panel_upper housing_e interior_frame01 pilot_panel_upper pilot_arm_panel cockpit_interior_panels center_console copilot_floor center_console_upper cockpit_back_plate pilot_panel_lower screws_small side_panel annunciator_panel master_test_panel pilot_lower_panel copilot_center_panel Center_Copilot_Panel canopy_glass_rear CoPilot_Panel armament_control_panel ecm_control_panel fuzing/master_arms_panel bombardier_panel nav_panel nav_control_panel attac_nav_panel ic_ir_cooling_control_panel copilot_instrument_panel canopy_glass_sides panal_small center_divider_panel small_plate_divider center_overhead_bar canopy_glass_front mirror_frame_right1 mirror_right1 mirror_frame_left2 mirror_left2 mirror_frame_left1 mirror_left1 window_trim_front housing_c //!!!!!!!!!!!!!!!unused gauge, not sure of needle!!!!!!!!!!!!!!!!!!!!!!! gauges14 gauges15 //!!!!!!!!!!!!!!!!!!!unused knobs,switchs and buttons!!!!!!!!!!!!!!!!!!!! knob7 knob08 switch_d02 switch_d04 switch_d03 switch_d05 switch_d07 knob09 knob2 knob3 knob4 knob10 knob17 knob25 toggles02 toggles03 armament_control_panel_knobs Button_Missile02 Button_Missile Button_Missile01 Button_R_Fire //Warn_RFire (used) Button_L_Fire //Warn_LFire (used) Button_L_Master_Caution //Warn_LMaster_Caution (used) //!!!!!!!!!!!!!!!!!!!! these needles are shown in cockpit but not used, can be used for ACLS indicator!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! intergrated_positon_indicator power_trim_a needle_power_trim_a power_trim_a01 ??needle_power_trim_a01 //--------------------------exhaust temp //exhaust_temperature_b01 //needle_exhaust_temperature_b01 //exhaust_temperature_b02 //needle_exhaust_temperature_b02 //--------------------------accelerometer //b-6_accelerometer //needle_b-6_accelerometer //b-6_accelerometer_knob //!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!not used!!!!!!!!!!!!!!!!!!!!!!!!!!!! gauge_uhf uhf_channel_frequency //-------------------------fuel qty //guage_fuel_quantity //needle_fuel_quality //!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!useful handles, to be mapped to functions!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! brake_selection_handle hook_release_handle lever_02 handle_pilot handle_copilot emergecy_stores_jettison canopy_switch canopy_jettison_handle master_caution_reset_button //-----------------------------MAP display under the radar screen, cannot be used for radar or rwr purposes for some reason-------------------------------- //phd //Phd_Needle //phd_lens //phd_dial (this item is the ring outside map display, however the Y axis is not centred, hence not usable) //-----------------------------WSO screen, currently used for RWR, has no dedicated lens node, texture must match existing 3d structure or it looks ugly------------------- //DVI2

I have actually created a "OUT" file. Although there is no hierachy. There are still bits and pieces I like to work on the A-6 pit. So Cockpit.ini may come later. The above picture actually contains 1-2 modified stock texture that I made to enable RWR

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?

the rwr is ALREADY at WSO side, check the picture above. plus the map is working. I tried to put RWR on ACLS next to hud but there are some ugly polygons pop out. so it end up at WSO side. I have gone thru the LOD and find all nodes. There are some unused one that may form a functional ILS/ACLS if lucky (hopefully ALCS lens is not awry). It has also been a surprise that such a pit has no pylon select indicator, no break handle, no gear handle, ho hook handle, no radar mode indicator... etc for so many years, and no one attempt to fix it. Now that I have a chance I'm going to get it right once for all

aethetically the stock TW is better. it blends in game and the lag to game is low

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.

unfortunately no. There is no .OUT file that I can find. Tried a few possible entries by looking in the LOD file directly, they are incorrect.

I assume they come from line diagrams in sketchpads... Put it simple this way, there is no game as far as I know that models Chinese J-7 before SF. Where could they come from?

OK, tested a few times. Obviously the author was ambitius, there are nodes for moving map and RWR left in the model. However the technique to swap MFD display was not discovered by the time and the author possibly given up due to the difficulty. Thus those were left in the model not functioning.

I have noticed there are RWR/TEWS definition in F-117 mod, and corresponding textures. However I can't find a way to get the screen show up in the MFD. Anyone knows how to?

Thanks for the update

Back in roughly half-a-year ago there were discussions of an A-37B for SF2. Can anyone let me know if it was released? Can't seem to find it with forum search..

should work for SF1

why would you ever need one from Capun if there is already one in Combatace... search for my files in combatace.

Well, did notice a bug... In the options, you can no longer select "in the air, near base".

I know this is probably way too much, but can we possibly have back seat for F4 for the 1st time?

View File Mig-31BM Mini Update Pack Out of 3 Mig 31 models available in CA (not sure why Mig-31A got removed...) Mig 31BM has the oldest model dated back to 2008, which has problem casting shadows and is over-polygoned. This package contains models changed late 2010 with multiple level of details and correct shadow casting. So that you can finally ditch the SHD file. Original creator : jv44 Skin: jv44 Please note the new model is not compatible with any previous skin. This update is released as-is. You will need to download & install Mig31m/bm pack from Brain32, then update with this mini pack. Find Brain32's file here http://combatace.com/files/file/9474-mig-31m-bm-foxhound-sf2/ Submitter orsin Submitted 05/08/2013 Category MiG-31

Well, the formula used in the tool is based on actual game experiment. I.e. we experiment on actual game with debug window, then we find the formula that match it. This is generic blackbox method. You can very much expect the simulation close enough to actual game performance in WOI - 2008 code base. If SF2 changed something in code then there could be a difference

I am not the author of the software so my interpretation is just guesstimation. From my understanding the software requires parameters such as missile acceleration at different stages, launch altitude and launch platform speed. so that it evaluates the range of the missile. The air friction varies at different altitude in game, and we found it is in general a linear function of speed given the altitude is constant. Now, regarding the "sonic speed", I may have misinterpreted its use. however please not there are plenty of Mach-altitude tables online. Which are in contrast of your mention, but could have been deduced from experiential function of air density and average temperature....

well, I assume the sonic speed means the actual 1Mach speed at altitude. I assume the sonic speed means the actual sound speed at simulation altitude, such that an entry will contrast with ground sound speed, and help achieve the IAS/TAS ratio. As for the Gs, they could be acceleration Gs for booster and sustainer, etc. With the help of this tools, we were able to adjust most of missiles. Even stock US/NATO missiles are way off accuracy. After adjustment, we were able to see missile speed slow down to less than 1mach at max range. They struggle to catch up any air target in max range

there is a special tool by HoneyFox that evaluates missile performance in download section. Most of missiles need adjustments in order to align with their real world performance.

there is a bug in its INI definition somewhere. I found it long ago. Once you you fix it, they become very lethal..