PREPAR3D V5 HOTFIX 2 COMPATIBILITY STATEMENT

Lockheed Martin has released P3Dv5 Hotfitx 2 a few days ago - hopefully it solves some of the stability/CTD issues that some of you told me about.
Apart from the stability issues, you may have noticed that some night effects (external lights, landing lights and VC illumination) are too bright and lights behave as "X-Rays". The excessive intesity is due to new parameters introduced in P3Dv5 (which only affect PBR materials), while the "x-ray" effect is unfortunately due to the graphic engine of the sim.
I'll try to find the time to update the effects on my older planes.
In terms of compatibility of my planes, nothing has changed...so here is the situation.


M-346 MASTER - Works fine, no issues to report.

F-35 LIGHTNING II - As previously noted, you need version 3.67 or above for it work fine with P3Dv5. Apart from that, and the excessive brightness of some effects at night, there are some minor issues with the voice alerts.

EUROFIGHTER TYPHOON - Works fine, except the excessive night lighting...which is particularly annoying since the landing lights illuminate the cockpit.

TA-4J SKYHAWK - Again, works fine except the excessive night lighting.

A-4E/F/G/H/I/K SKYHAWK - Same as above.

C-2 GREYHOUND / E-2 HAWKEYE - They should work fine, as they do not have PBR effects.

S-211/M-345 PROTOTYPE - They should work fine as there are no PBR effects in the cockpit.

PROJECTS ROADMAP UPDATE - JUNE 2020

As the M-346 is approaching the public release, I thought it was time to share my current plans.
This is basically what I have on my hard-disk...in no particular order. Completion of the projects will depend on a number of factors.

The general plan is as follows:

- Lead platform: for the time being, the lead platform is still Prepar3D V4.4 / v4.5 /v5.0. The lead platform may change in future. The general idea, however, is to pick the best platform for each project depending on where it will be possibile to create the best product.

- Microsoft Flight Simulator: the plan is to support the new Microsoft Flight Simulator, initially by converting the planes we thing are most fit for conversion and with proper quality.

- X-Plane 11. Still some work going on with XP-11...mostly conversion of existing projects.

- Other platforms: we are actively working on partnerships and cooperations.

F-35 LIGHTNING II - VERSION 4.00 for MSFS / P3Dv5

The general idea is to have a new baseline of the F-35 project, rebuilt to comply with MSFS standard.
At the moment, however, STOVL capabilities in MSFS are unclear… so the project is limited to the F-35A for the time being.
PROJECT STATUS: PRELIMINARY WORK

TA-4J FOR X-PLANE 11

The conversion is almost complete...it just needs some minor tweaks to the flight model and avionics before moving to the Beta stage.
PROJECT STATUS: ALPHA BUILD COMPLETE

MC.72 for MSFS / P3Dv5 (and XP-11 maybe?)

The Macchi Castoldi MC.72 is established the world speed record in 1934, and held it until 1939 and is still, to date, the fastest piston seaplane ever built. I thought it would be fun to have one in the sim.
PROJECT STATUS: PRELIMINARY 3D MODELING

F-14D SUPER TOMCAT REBUILD for MSFS/P3Dv5

The idea here would be to rebuild from scrathc my F-14D Tomcat. Given the high quality of the F-14B in DCS, the interest on this project may not be great. Still it is looking cool.

PROJECT STATUS: ON HOLD - PRELIMINARY 3D MODELING COMPLETE - NOT ENOUGH RESOURCES AT THE MOMENT.

BOEING T-X for MSFS/P3Dv5
I quite like this plane...but at the moment the infomation on the cockpit and the avionics is scarce. Waiting for more info.
PROJECT STATUS: ON HOLD - AWATING MORE INFORMATION

BOEING MQ-25 STINGRAY for MSFS/P3Dv5
This started as an experiment to make a naval drone. Looking good and seems a great complement to the F-35 in some scenarios.
PROJECT STATUS: 3D MODELING COMPLETE - NOT ENOUGH RESOURCES FOR THE MOMENT

BOEING T-45 GOSHAWK for MSFS/P3Dv5
I had started a remake of the Goshawk project… but there may be competing products in development...so no further progress has been done.
PROJECT STATUS: ON HOLD - POTENTIAL CANCELLATION

M-345 for MSFS/P3Dv5
There is now some information available on the new M-345 trainer...and it would be cool to transform the M-345 prototype in the M-345 production model.
PROJECT STATUS: ON HOLD - DOCUMENTATION REVIEW

PREPAR3D V5 COMPATIBILITY LIST

Prepar3D V5 is out...and while it is not the revolution that many were waiting for, it is definitely a step forward thanks to its DirectX 12 implementation, better atmospheric and water rendering...and a ton of bug fixes and small improvements. However, I think many users are waiting for FS2020 and will not make the jump to this new version. Also, a lot of the "combat" user base of FSX/P3D has jumped to DCS following the slow (but steady) release of high quality aircrafts. 

Also, please bear in mind that, at least at the moment of writing this post, VRS TACPACK is NOT COMPATIBLE WITH P3Dv5 and I have no idea if and when VRS will update it. Therefore, my planes WILL NOT have full functionality in P3DV5 (radar, weapons, configurator, chaff-flares,
ECM, FLIR and other sensors will not work). 

Anyway here is the compatibility list for my commercial projects:

EUROFIGHTER TYPHOON - works fine in P3Dv5, but update to PBR is highly recommended (see payware projects) 

F-35 LIGHTNING II - REQUIRES NEW INSTALLER (v3.67) SEE PREVIOUS POST ON THIS BLOG. Older versions do not work due to a file naming conflicts with Lockheed Martin Assets 

SIAI MARCHETTI S-211 / AERMACCHI M-345 PROTOTYPE - works fine in P3Dv5, but update to PBR is highly recommended (see payware projects) 

C-2 GREYHOUND / E-2 HAWKEYE PACKAGE - both planes work fine. No PBR update available. 

TA-4J SKYHAWK - works fine in P3Dv5 

A-4E/F/G/H/K SKYHAWK - works fine in P3Dv5

TA-4J for Flight Simulator X Beta Test

As promised, and due to the large number of requests, I have created an FSX version of the TA-4 Package (which should work also on P3Dv2 and v3).

With respect to the P3Dv4 version:

- There is no backseat/instructor cockpit

- The 3D materials are "traditional" (as opposed to PBR)

- The radar image is based on the old FSX mapping service (as opposed to P3D "true" radar rendering system)

Apart from some other minor details, pretty much everything else is the same as the P3Dv4 version...including flight model, options and system simulation.

The package will only work with FSX:A, FSX:SE, FSX:Gold...and should work (but it is not tested) with P3Dv1, v2 and v3.

Before releasing the package, a quick Beta test is needed, but it will be limited to few testers.
If you want to apply for the testing, please send me an email with "TA-4J BETA FSX" as subject and specify:

- your CPU, GPU and RAM

- OS

- which version of FSX you are using

Ideally the testers should have flown the P3Dv4 version for a functionality comparison.

Please find below the usual Bugs/Change request list (I expect it to be EXTREMELY short as we solved a lot of bugs in P3Dv4...fingers crossed)...

TA-4J for FSX BUG REPORT AND CHANGE REQUEST LIST

Last updated by Dino on 05/10/2019 at 13:15

FLIGHT MODEL

VISUAL MODEL

VIRTUAL COCKPIT

OTHER

TA-4 Skyhawk for P3Dv4.4 version 1.07 released

The TA-4 package has been updated to version 1.07...here are the full release notes:

CURRENT VERSION: 1.07
VERSION 1.07 - October 3rd 2019
- Fixed issue preventing ground service carts from showing if selected by the menu
- Slightly reworked mirror effects
- Fixed ADI and backup ADI behavior (hopefully)
- Fixed missing 3D screws in rear cockpit
- Added VMAT-102 repaint courtesy of Matt Levi
- Added VF-43 repaint

There is a small mistake in the VF-43 textures, as the high visibility roundels are missing from the wings… updated textures can be downloaded HERE

TA-4J Post Release Change Request Log

Thank you all for you great feedback and for the support to the TA-4J. I have received many suggestions for improvements so here is a a post that serves as collector of the post-release changes requests….

POST RELEASE CHANGE REQUEST LOG
Last updated on 03/10/2019

LATEST VERSION RELEASE: v1.07

GREEN - Fixed and released
BLUE - Fixed but not released
RED - Open, high priority
YELLOW - Open, low priority

PR001 - Bug causing the canopy glass and the copilot compass screws not to move when canopy opens: Fixed, implemented in v1.02
PR002 - Gunsight not occluded by glass geometry: Fixed, implemented in v1.02
PR003 - Bug causing the Radalt "OFF" flag to be always on: Fixed, implemented in v1.02

PR004 - Incorrect copilot suit color for Blue Angels scheme: Fixed, implemented in v1.02

PR005 - Fixed bug allowing non-tacpack users to load fuel on external tanks even if tanks were not fitted: Fixedm implemented in v1.02

PR006 - Fixed visual collision between Bullpup missile and front landing gear stem: Fixed, implemented in v1.02
PR007 - Fixed missing "518" number in flap suface for N512TA livery: Fixed, implemented in v1.02

PR008 - Minor modification to default viewpoint: Fixed, implemented in v1.02

PR009 - Incorrect indication of pitch during inverted flight: Fixed, implemented in v1.05
PR010 - Incorrect behavior of RADALT flag: Fixed, implemented in v1.05

PR011 - In reality MK-82 and MK-82SE bombs were not be carried in the innermost stations of PYL 2 and 4 as the gear door could not open fully, implemented in v1.05

PR012 - Request to add Aero adapters to sidwinder launchers: STATUS - Fixed. Modeled adapters and modfied code. Implemented in v1.05

PR013 - Incorrect loadout assignment to STA1 and STA5: STATUS - Fixed: restriced loadouts on STA1 and 5. Implemented in v1.05

PR014 - MK-82 bomb hung at centerline pylon in certain conditions while operating the configurator in non-Tacpack mode. FIXED, completely rewrote code, implemented in v1.05

PR015 - 300 gal tank fins too narrow. STATUS - FIXED. Redone fin geometry. Textures are a bit stretched...but at this point this is the best I can do. Implemented in v1.05
PR016 - Improper Aero adaper for AGM-12 and AGM-45 - Fixed. Implemented in v1.05
PR017 - Gunsight day and night colors are swapped - FIXED: swapped bmp file names. Implemented in v1.05
PR018 - Gunsight can be powered on even if there is no electrical power. FIXED - Implemented in v1.05

PR019 - Air and electrical doors receptacle doors do not work as intended. FIXED - Implemented in v1.05

PR020 - ADI still does not work as intended, also backup ADI now locked in pitch. Fixed. Implemented in v1.07
PR021 - Electrical power cart blinks and disappears if selected by menu. Fixed: implemented in v1.07
PR022 - Some missing screws in the rear seat model. Fixed: implemented in V1.07
PR023 - Try and improve mirror reflection. STATUS: open. Effect is now slightly better but resolution is poor.
PR024 - VF-43 fixture has missing roundel. Fixed, but not released in full installer: updated texture can be downloaded here.
PR025 - Revise button shortcuts for "ready to start" condition
PR026 - Create new radar controls for future implementation of proper A/S radar
PR027 - IFF Tacpack controls INOP

TA-4 Skyhawk P3D v4 Release and Paintkit

With thanks to all the people involved in the development, and in particular to Roy Holmes for another great flight model, I glad to announce that the TA-4 Skyhawk/Scooter package is now available for purchase at SimMarket.

As normal for this kind of projects, a couple of minor glitches popped-up after release… no major issues at the moment. I am working to solve this, but I will wait another week before releasing an update - just in case more bugs are identified in the short term.

Also, the paint kit is now available for download here. The TA-4 had some of the best and flashiest liveries ever seen in a miltary jet… and picking the ones to include in the package was not an easy job. Can't wait to see what the community will create!

Aside, an FSX version and a single seater are both in the works...more news soon.

TA-4 Skyhawk for Prepared V4.4+ Flight Manual

Should you be interested in seeing what the TA-4 for Prepar3D v4.4 does (and does not) simulate, HERE is the (tentatively final) flight manual…

Most of the text was taken from an old TA-4F/J manual scanned into a .pdf file… I used an OCR software to extract the text, but there were a number of characters and words misinterpreted by the software (and then English is not my first language) - I got rid of a number of those errors but still there are dozens of them. Corrections and proof-reading are welcome.

Major deviations from real world flight manual are highlighted as "SIMULATION NOTE(s)" - meaning that what follows is valid in the simulation only and may not apply to real life.

Manual can be downloaded by clicking HERE.

Last, the Release Canditate 1 Build is complete - it will be distributed ASAP (unfortunately I am a little busy in these days) - on the good side (basic) implementations of NWS and APC systems were added. The latter is not super-precise, but kinda works - up to you to tell if it actually helps you in Landing on the boat or not

TA-4J Skyhawk for Prepar3Dv4.4+

As per my usual procedure, here is the post meant to collect the feedback from the TA-4J Beta Testing. This is (almost) constantly update with the "accepted" bugs and suggestions, color coded to reflect their status. "Accepted" means that I have understood what the testers reported, I could replicate it (or at least be sure this is not a misinterpretation or an error from the tester) and I have "accepted" it as a item to be addressed.

RED means that it the defect has been categorized as a major issue. This is typically a showstopper (operation of the aicraft is impossible or severely inhibited) and must be addressed before the product release.

YELLOW means that it is definitely an issue for the project, that should be addressed before the product release, but not as critical as a "red" issue

GREEN means that either the issue is very minor (and will not be noticed by most users), or the problem is non-existent (feature reported as bug) or that is was an red or Yellow issue that has been solved

BLUE means suggestions or ideas to improve the product

I am not sure if a flight manual will be available before the Beta is released, most probably not, but here are some peculiar things you need to know before operating the aicraft.

Starting the engine

The TA-4 required external air power to start the engine. You can make the "Huffer" appear by selecting it in the configuration menu (SHIFT+4), but it will only appear if the aircraft is not stationary and parking brakes (wheel chocks) are not applied (icon is greyed out otherwise). You can make it appear also by clicking on the external air power connection door.
To start the aircraft you will need also electrical power (see below)

Electrical System

The TA-4 had no internal batteries. This means that the aicraft had its own electrical power only if the engine was running. The TA-4 had also an emergency generator which is not simulated.
To get electrical power while the engine is not running an external electical power cart was needed. You can make it appear and connect it to the aicraft on the ground by selecting it in the aicraft configuration menu (SHIFT+4) if the aircraft is stationary with parking brake applied (wheelchocks appear) or by clicking on the external electrical power door.

Fuel System
The fuel system is simulated in some detail and requires a good understanding of the real world one to be operated.

Weapon System
In order to fire a weapon, you must:
- Select the type of weapon you intend to use
- Power the relevant pylon
- Set the Master Arm Switch to ON
- Press the TRIGGER for forward-firing weapons (guns, rockets and missiles) or the PICKLE button for bombs.

Radio and Navigation System
- Combined Radio/ADF selector: will work as COM1 if set on primary, COM2 if set on both, ADF if set to ADF
- The NAV computer is not operational, but works as a GPS display
- The BDHI pointer 1 will always show the NDB station
- The BDHI pointer 2 will display: the next WP in the flight plan if set to NAV COMPUTER or the TACAN station if set to TACAN
- Note that TACANs are implemented in the legacy FSX version, that is channels are converted in frequencies and used as NAV1 instrument.

Flight Model
As far as we can tell, the flight model is pretty close to the real deal...but I can already see some of the comments about the roll rate. The A-4 family is famous for having an exceptionally high roll rate, and you can read several Pireps or see video interviews of pilot claming that the peak roll rate is 720°/sec. However (apart from the fact that rolls of more than 360° are explicitly forbidden by the flight manual) actual data points you can find on the internet seem to indicate that the real roll rate was lower (highest value measured I could find is 410°/sec). Current flight model is set to for a a peak of about 350°/s, which seems to be a realistic figure.

FLIGHT MANUAL

Flight manual will be available shortly and will be available for download HERE.

REPAINTERS

The Beta model is NOT intended for repainting. A full paint kit will be available at the release.

TO DO LIST
Actions that have already been planned but are have not been implemented:

- Make the NAV COMPUTER selector knob functional
- Implement white flood lights
- Implement correct visibilty conditions of the approach light
- Implement pocket checklist (placeholder at shift+5, no function)

TEST TEMPLATE

If you want to, you can use THIS template as guideline/checklist for the tests

REPORTING BUGS

The preferred way to report bugs is to post a comment on this blog (so that everyone can see it). Otherwise, email messages with "TA-4J Bug Report" as subject are fine.
It is better, before posting, if you check if thebug you have spotted is already in the list below or in the comments.
Bugs or change request are evaluated ASAP and, if confirmed and accepted, added to the list below.

ACCEPTED BUGS AND CHANGE REQUEST LIST
This list was updated on 23/08/2019 11:00AM CEST
The latest Beta version is 1, released on 21/07/2019
Internal Beta (not released) version 1.10 last built 23/08/2019

Total lines (excluding suggestions) 79
Current red lines 0
Current yellow lines 8 (of which 4 rejected for various reasons)
Current green lines 70
Current blue lines 1
Progress towards release: 88%

EXTERNAL VISUAL MODEL

TA4P3DEXT01 - Horizontal Stabilizers not sitting at the same angle? STATUS: small asymmetry in elevator postion detected. FIXED
TA4P3DEXT02 - Texture N518TA, Naval Aviation Anniversary decal reversed. FIXED.
TA4P3DEXT03 - Animation of horizontal stabilizer trim is reversed. FIXED
TA4P3DEXT04 - Blue Angels logo is wrong (it is the current BA logo with Hornets). STATUS: CLOSED (reworked logo)
TA4P3DEXT05 - Need to add specific uniforms/suits (at least for BA). STATUS: CLOSED

TA4P3DEXT06 - Request to add separate textures for front and rear pilot. IMPLEMENTED

TA4P3DEXT07 - Request to add animated pilots. IMPLEMENTED PILOT ANIMATIONS (arms, legs, heads).
TA4P3DEXT08 - VC-8 Aggressor livery typically had inner flap surfaces painted in red. STATUS: CLOSED (reworked texture).
TA4P3DEXT09 - Request to add chrome finish details to BA livery. STATUS: CLOSED (implemented)
TA4P3DEXT10 - Request to improve PBR materials on non-shiny liveries. STATUS: IMPLEMENTED
TA4P3DEXT11 - Request to improve PBR materials for selected details. STATUS: IMPLEMENTED

TA4P3DEXT12 - Approach lights should show only when tailhook is down or field bypass is on.
TA4P3DEXT13 - Revised wheelchocks condition. Wheelchocks now appear when park brakes are on. Skyhawks do not have park brakes, so setting them will activate the wheelchocks.
TA4P3DEXT14 - Need to add holdback bar. ADDED

VIRTUAL COCKPIT MODEL

TA4P3DVC01 - Gunsight assembly is slightly too big. STATUS: CLOSED. Added space for LOCK-ON and IN RNG advisory (alternate gunsight as used by later Skyhawks).
TA4P3DVC02 - Typo "attack" mode is misspelled. STATUS: CLOSED - Fixed typo in texture master layer.
TA4P3DVC03 - Gunsight crosshair not masked during High-G maneuvres. STATUS: OPEN - Difficult to fix without creating other issues, leaning towards keeping it as is. Not completely solved but much improved. Also, calibrated gunsight size.
TA4P3DVC04 - Request to minimize the stick visibility area. STATUS CLOSED. Now to make the stick visible again you need to click very close to the jettison handle.

TA4P3DVC05 - Request to reduce size of radios and GPS. STATUS CLOSED

TA4P3DVC06 - Rear cockpit POV lower than the front. STATUS CLOSED - Harmonized POVs but not completely identical (front one has to match the gunsight)
TA4P3DVC07 - Request to make PR bug operational. IMPLEMENTED

TA4P3DVC08 - Request to make airspeed bug operational. IMPLEMENTED

TA4P3DVC09 - Request to make RALT bug operational. IMPLEMENTED

TA4P3DVC10 - Request to implement AOA bug. IMPLEMENTED
TA4P3DVC11 - Typo fuel dump switch marked as "dump": STATUS: TO BE CHECKED. Note that a pilot-controlled fuel pump exists in the cockpit and serves to transfer fuel to from the wing tank to the fuselage tank - FIXED
TA4P3DVC12 - Check Pitot Anti-Ice Switch functionality. FIXED
TA4P3DVC13 - Check Engine Anti-Ice Switch functionality. FIXED
TA4P3DVC14 - Machmeter is currently a fixed scale (as opposed to rotating). Check if it possible to make it working against altitude. FIXED
TA4P3DVC15 - Request possibility to have more realistic lighting system (external lights). Note: at present the Aircraft implements only the default lighting system. - REJECTED, for code compatibility reasons.
TA4P3DVC16 - Request possibility to have more realistic cockpit lighting system (user controlled lights than can be dimmed) - REJECTED, for code compatibility reasons.
TA4P3DVC17 - Check AFCS ENGAGE button (seems reversed) - CHECKED. Switch was reversed, also note that autopilot in P3D will not activate if avionics are off, so it will not activate if radios are off in the TA-4J!TA4P3DVC18 - Check ALT HOLD function - IMPLEMENTED, also solved a bug preventing heading hold from working
TA4P3DVC19 - Check AFCS panel functionality - FIXED. Autopilot master, yaw damper, alt hold, hdg hold now functional.
TA4P3DVC20 - Request to move GPS to other positions - Resized, moved to position 6
TA4P3DVC21 - Fuel system lights comes on when PRIMARY fuel control is selected (as oppesed to manual) - FIXED
TA4P3DVC22 - Flood light switch. FIXED. Flood lights were incorrectly tagged.
TA4P3DVC23 - Movement of the backup trim switch is reversed. FIXED.
TA4P3DVC24 - Elevator Trim Indicator Needle has a reversed animation. FIXED.
TA4P3DVC25 - Some switches of the right side light/ecs panel do not work. FIXED, although those switch had no fuction.
TA4P3DVC26 - AoA indexer in instructor cockpit not working. FIXED
TA4P3DVC27 - Recalibrate gunsight with new geometry. FIXED
TA4P3DVC28 - Missing Armament Advisory Light. FIXED
TA4P3DVC29 - Need to redo AoA Indexer visibility conditions. FIXED
TA4P3DVC30 - AoA flag visible even if power is on. FIXED, redone code for all flag animations.

FLIGHT MODEL:

TA4P3DFM01 - Ground steer radii too big? STATUS: to be verified. Modified to 70 degrees - CLOSED.
TA4P3DFM02 - Request to implement proper NWS
TA4P3DFM03 - Excessive fuel burn rate (potentially a bug in the fuel system)? STATUS: WRITTEN OFF (tester error)
TA4P3DFM04 - Speed brakes do not completely rectract (possibly a bug in the speedbrakes blowback feature?) STATUS: TO BE VERIFIED. Checked. Spoilers open/close correctly. Claim of tester was probably due to the fact that the time required for the light to go off is relatively long if the pilot uses digital spoiler control. Changed light condition so that the caution light turns on only if spoiler is deployed more than 25%.
TA4P3DFM05 - Tendency to tipover during arrested landings. - FIXED with better tailhook configuration settings.

OTHER:

TA4P3DMISC01 - Bug in the airplane configuration manager (most likely in the SMS system code): if Tacpack is not loaded, missile rails fail to appear when they should (all stations). STATUS CLOSED. Wrote special case code for when Tacpack is not loaded.
TA4P3DMISC02 - Bug in the airplane configuration manager (most likely in the SMS system code): if Tacpack is not loaded, external fuel tanks are always present (regardless of user selection). Status:CLOSED. Wrote special condition code.
TA4P3DMISC03 - Bug in the airplane configuration manager (most likely in the SMS system code): if Tacpack is not loaded, it is possible to have both the MK83 and BDU33 bombs on the centerline store. STATUS CLOSED. Several other bugs squashed.
TA4P3DMISC04 - Suggestion to make the smoke effect optional - Implemented
TA4P3DMISC05 - Suggestion to make the switches and knobs with multiple positions to work in both directions (currently they are "one way" as I thought it was easier for VR) - Reprogrammed all multiple position switches and knobs so that they now react to mouse wheel.
TA4P3DMISC06 - Suggestion to add cold and dark/ready to taxi option. Added control+shift+R as ready to start. The Aircraft will default to cold and dark.
TA4P3DMISC07 - Tracer bullets in visual effects shoot too high. STATUS:CLOSED. Significantly lowered tracer trajectories.
TA4P3DMISC08 - Sound Cone settings are so that engine noise is very quiet from some angles. STATUS: CLOSED. Mantained sound cone (as they work pretty well in the air) but redone engine samples.
TA4P3DMISC09 - Cannot launch from default and Javier's carriers (works only with SWS)… FIXED: Following entry should work and fix the issue:
[launch_assistance]s
launch_bar_pivot = 5.95, 0.0, -1 
launch_bar_lug = 5.95, 0.0, -7.9  
TA4P3DMISC10 - Control+SHIFT+C "Gun ready" shortcut does not seem to work - FIXED. Now orks as intended, also added W shortcut to for weapon selector.
TA4P3DMISC11 - CONTROL+J "Selective Jettison" shortcut does not seem to work - FIXED. Works as intended in conjuction with the EMER SEL allows the release of a given pylon. Also implemented CONTROL+SHIFT+J as "Emergency Jettison" (releases all bombs).

TA4P3DMISC12 - Control+SHIFT+W "Weapons Reload" shortcut does not seem to work. Works as advertised in the program (but you must be in VC).
TA4P3DMISC13 - Suggestion to include the TACAN Frequency conversion table. Added to both pocket cheklist and manual.

TA4P3DMISC14 - Suggestion to allow the user to select either the P3D or FSX TACAN system

TA4P3DMISC15 - Manual: LoP Para 3 line 1 "and" misspelled. Fixed in manual.
TA4P3DMISC16 - Manual: LoP Para 4 line 2 "of" missing. Fixed in manual

TA4P3DMISC17 - Manual: Para 1, missing words "of the aircraft in"
TA4P3DMISC18 - Igniters and other spelling errors present (Note, most of the manual comes from NAVAIR 01-40AVD-1 "NATOPS FLIGHT MANUAL NAVY MODEL TA-4F/TA-4J through an OCR software from a not-so-great source file, so multiple misspelling errors are possible). - FIXED TO THE BEST OF MY POSSIBILITIES.
TA4P3DMISC19 - Potential errors in the NAV1 to TACAN conversion decoding - STATUS: SOLVED: minor bug found in VHF to TACAN conversion code. NOTE: it may also affect other aicrafts of mine where the TACAN is not set directly, but throgh VHF frequency and then converted.

TA4P3DMISC20 - Request to add support for P3D TACAN system. REJECTED for code compatibility reasons.

TA4P3DMISC21 - Request to add support for TACPACK navaids - IMPLEMENTED

TA4P3DMISC22 - Request to add support for SWS navaids - IMPLEMENTED
TA4P3DMISC23 - Uncommanded SW release if guns selected - STATUS: SOLVED. Major mistake in the weapons code was energizing STA 1 circuit instead of circuits 14 and 15 (guns). This also explains why hitting targets was so difficult.
TA4P3DMISC24 - Allow airstart even if power is not connected if enough air is blowing through the compressor - FIXED
TA4P3DMISC25 - Request to implement LOCK-ON advisory light
TA4P3DMISC26 - Request to implement IN RNG advisory light

TA4P3DMISC27 - Request to implement CCIP - IMPLEMENTED
TA4P3DMISC28 - Add Pocket Checklist - IMPLEMENTED
TA4P3DMISC29 - Add visible feedback when the Aircraft is ready for catapult connection - IMPLEMENTED new configurator menu
TA4P3DMISC30 - Added basic A/A radar.

PRE-RELEASE ACTIVITIES

PRODUCT MANUAL - Missing weapon usage information, needs to be updated for the addition of new features (e.g. navigation system and CEX support) - UPDATED PRODUCT MANUAL COMPLETE!

TACPACK MULTIPLAYER VALIDATION - TACPACK MULTIPLAYER VALIDATION COMPLETE!

INSTALLER - TBC

RELEASE CANDIDATE 1 RELEASE TO TESTERS - TBD

EOF

TA-4J Skyhawk for P3Dv4.4+ - Beta Test Application

I know that many of you were waiting for this so here we are with the Beta Test application post of the TA-4J for P3Dv4.4 and above - so, if you are willing to help with the testing, in this post you will find the instructions to apply.

A brief introduction to the project: this is the first project I have designed from the ground up to support specifically P3Dv4.4 / P3Dv4.5 features and above - basically with no regards with the limitations of the FSX compiler. At the moment, I plan to try and downgrade the model in future for FSX compatibility as a separate project… but early attempts failed and it is not granted that it will ever come to FSX.

As with any simulation, it is basically impossible to include each and every feature of the real aicraft, but my hope is that this may be the most complete rendition of the TA-4J to date (fingers crossed).
I am sure I left something important out...so, if you are selected for the test, you are encouraged to suggest additions and improvements.

As usual, I am looking for testers with various level of aviation experience and skill, but I am looking in particular for users who know the TA-4J aircraft and a passion for naval aviation.

Hardware requisites (suggested configuration):

- Quad core CPU with at least 2.8GHz clock

- 6GB minimum RAM, 8GB better

- Nvidia 960 video card or better, 2GB dedicated video memory minimum 

- 1 GB minimum free disk space for package installation

Software prerequisites:

- Lockheed Martin P3Dv4.4 or v4.5

- VRS Tacpack required for weapon functionality

As usual… the Beta tester for my projects is not a paid position, by any stretch of the imagination: you do it just for the fun of doing it.

If you are willing to help, send me an email to indiafoxtecho.gmail.com - the email shall contain:

- a BRIEF description of your system (no need of minor details, I just need CPU type and clock, RAM, video card and video memory)

- a brief description of your real world flight experience (if any) including (if any) your knowledge of the TA-4J Aircraft (note… the Beta is open to everybody: from teenage desk flyers to WWII aces - I just need to know who I am talking with!). No need of long and detailed stories...just a line or two will do.

- your experience with Prepar3D v4

The topic of the email shall be "Prepar3D v4 TA-4J Beta Testing" (note...I thought this was an easy requirement, but apparently it is not...but it is very important: it helps me a lot sorting the messages and it shows that you can comply with instructions).

Note it may take 2-3 weeks to reply and provide a download link… so be patient.

PROJECT ROADMAP FOR 2019

The E-2/C-2 project is close to completion, and given that this 2018 is slowly approaching to its end, I though this was a good time to share my current projects for 2019.
But first, let me thank you once again for your continues support to my projects - you enthusiasm and appreciation for what I do is much appreciated!

So, let's start with the easy things...

 UPDATES TO CURRENT PROJECTS:

As usual, I'd like to keep my projects up to date whenever possible...so here is what I am working on:

SIAI S-211 - A small patch is in the works to fix a couple of minor glitches. I am also looking to add a couple of liveries, a (much requested) smoke system and some sort of aiming support for weapons release (at least for the HUD-equipped versions). At least the glitches will be fixed before the end of 2018.

F-35 LIGHTNING II - Minor fixes to the BFI and MFD, possibly new liveries. The patch will be for P3D versions only. Release is planned before the end of 2018.

EUROFIGHTER TYPHOON - Also for this one, fixes to minor glitches are planned. I'd like to rework some aspects of the cockpit model too...but I am not sure I can find the time. Release date TBD.

F-14D SUPER TOMCAT - Although this project was "closed" years ago, I've been working on a P3Dv4 version to provide full 64 bit compatibility and AO support. I am not sure when (and if) it will be ready, so release date is TBD.

NEW PROJECT: McDONNELL-DOUGLAS TA-4J

If you follow my Facebook page this is hardly surprising, but my next project will be the TA-4J. The scope is to deliver a high quality rendition of this aircraft. By similarity there is some chance that the project scope may creep towards the inclusion of the TA-4F and/or the A-4F...but at the moment the focus in on the TA-4J.
With the current pace, a Beta version may be ready in spring 2019.

Lead Platform is Prepar3D v4, but with backward compatibility to FSX:SE in mind.

Also, the model will be built with provisions for an easy export to other platforms.

External model of the TA-4J in P3Dv4.3... it is already 50% complete.

Very early look at TA-4J cockpit… it will require months of work!

NEW PROJECT: BOEING T-X

I have been following the TX competition quite closely - and I have to confess that, technically, my money was on the T-50. However, for a number of reasons, seeing the victory of Boeing/SAAB design was hardly surprising.
I have been working on a T-X model lately, although at the moment, the information about the cockpit and pilot interface is insufficient for a reasonably accurate simulation. Provided that more information will become available in time, the T-X project should be available before the end of 2019.
Lead Platform is Prepar3D v4, but with backward compatibility to FSX:SE in mind (but chance is that the MFD may be too complex for FSX...much like it was for the F-35).
Also, the model will be built with provisions for an easy export to other platforms.

Early picture of the Boeing T-X in P3Dv4.3

...AND NOW THE ELEPHANT IN THE ROOM: THE DECLINE OF FSX

As much as it is hard to admit it, I think that FSX is now technologically outdated, and its popularity is declining (albeit more slowly than most people predicted). And, while P3Dv4 is a good step forward, unless Lockheed Martin pulls a rabbit out of the hat with new shaders or a better rendering pipeline, chance is that P3D will follow. 

Continuing to support FSX is getting harder and harder, as basically you cannot use the new features of P3Dv4 if you want to maintaing backward compatibility - and developing multiple versions requires a lot of effort - especially if you are a small developer like me.

For these and other reasons, in the past years I have been closely looking at other platforms and made a number of experiments.

Still, at least for the TA-4J, I'll continue supporting both FSX and P3D as main development platforms. Then we will see.

X-PLANE 11

Unknown to most users, XP11 has a number of limitations in the aicraft modeling which make the conversion from FSX/P3D to XP11 not trivial (see the document I have published some time ago). Also, in terms of avionics, XP11 has almost everything you need for civil aviation...but not much for military planes, especially if they have digital instruments, MFDs and HUDs.

Anyway, I am moving forward with the conversion of the Siai Marchetti S-211, which feels at home in XP11, and, in 2019, the TA-4J. Given their avionics and cockpit features, they are relatively easy to convert.

I have been experimenting with the conversions of other aircrafts, too… but at this time I have nothing to announce.

The SIAI S-211 Flying in XP11 - it is almost complete...it just needs some work on the cockpit but it is already flyable.

AEROFLY FS-2 

While it is not much popular, I really like this sim for VR, sightseeing flights. Its excellent frame rate and high-resolution photoreal terrain make it the ideal showcase of my HTC Vive when friends come and visit me.

Unfortunately, with the current status of the SDK, developing aircrafts for this sim is very time consuming.

This is why I have recently released the unfinished S-211 for free lately.

I am not sure I'll have the time do other projects in future, but I'd like to, and then may be IPACS will improve the SDK. We'll see.

The SIAI S-211 in Aerofly FS2

DCS

The question I have been asked most in 2018 is, "Aren't you looking at DCS? Why don't you convert your planes for it?"...well… of course I've been looking at DCS. Below is a picture I took in an early attempt to convert the Eurofighter Typhoon to this platform.
However, the big problem with DCS is that it does not offer a "middle ground"...you either do simple mods (and rely on default functions) or you'll have to model each system on your own - which is very time consuming.
To develop a "decent" (and I am not saying "good" - by "decent" I mean FC3-level airplanes) you still need to assemble a good team, and it still requires a lot of work.
I am looking at different strategies for this, but, at the moment, no one is really a convincing way to move forward.

An early shot of the Eurofighter Typhoon in DCS - Don't hold your breath, at the moment it is just a test and may never become an actual product.

OTHER PROJECTS

...and that is not all. Back to FSX/P3D I have a number of other small projects on the drawing board… which include an MQ-25, the final release of the USS America model and the "pro" version of the T-45.

Also, I have been looking at making the M.C.72 as a divertissment, and I have been discussing cooperations for a number of other interesting projects - which I cannot disclose right now. The main problem is that I do not have much time - and, at the moment, quitting my real life job to only this is not an option...