WytchCrypt

Agreed. With my Hornet discount I paid $25 for the pre-order...$25!!! Back in the days of buying boxed PC flight sims off the shelf I would have gladly laid out $75+ for an add-on like this. Thanks to DCS, times are good for us military flight simmers :thumbup:

You betcha. I love DCS, where else is a 59 yr old color blind guy gonna do carrier ops :pilotfly:

Just did something I've never done before in my 3 years of flying DCS...a pre order! And since I only fly the Hornet & Su33 getting an updated Kuznetsov is gravy :smilewink:

Yes, that's what I was saying! Just letting those of us who are doing upgrades to a previously printed manual know which chapter & section needs to be printed from the new version and where to replace it in the old version :smilewink:

I'll answer my own question for anyone else who's curious. Part 9 - Radar & Sensors, there's a placeholder page for "TWS Coming Soon" :smilewink:

Hi all, I've recently completed uploading an Su33 skin based on the LSU Tigers 2019 NCAA Football Champion team uniforms, helmet and homefield logo. You can find the link at: https://www.digitalcombatsimulator.com/en/files/3307820/ Hope you like it and take it for a spin :pilotfly: Here's a few pix...

Hi all, just wanted to drop a line that I have 2 versions of what I call the "LSU Tiger Hornet" up on user files and available for download. These are both based on the 2019 College Football Champion LSU Tigers uniform, helmet & field logo. The original one posted a couple weeks ago, is a mostly off-white Hornet with understated gold & purple trim and LSU Tiger graphics. It lives at: https://www.digitalcombatsimulator.com/en/files/3307696/ The new one I call the "LSU Tiger Hornet Championship Edition", posted yesterday and is different from the original by adding: 1. Display of the plane tail# as set in the mission editor on the front gear doors 2. A new purple nose and more colorful curved wing trim paint design 3. "2019 NCAA NATIONAL CHAMPIONS" labels on the fuselage 4. Alternate version of the plane with record setting LSU 2019 Quarterback pilot name, "Captain Joe Burreaux" on the side included - spelled the Cajun way of course! It lives at: https://www.digitalcombatsimulator.com/en/files/3307860/ If you're interested and fly the Su33, I've completed one for it based on the Tigers alternate purple uniform...you can see it at: https://www.digitalcombatsimulator.com/en/files/3307820/ Hope you like them and give them a spin :pilotfly: Here's 3 pix of both (many more available on their user file pages)...first the original version... And now here's 3 of the "LSU Tiger Hornet Championship Edition"...

Yes, I've tested both: {"F18C_BORT_NUMBER_STV_aus_L_01", DECAL ,"empty",true}; & {"F18C_BORT_NUMBER_STV_aus_L_01", DECAL ,"empty",false}; with empty.dds in the directory...makes no difference, the box is always there. What's most important to note is this isn't just a problem in my own hornet skins, the box appears on EVERY default and other custom skins that aren't even mine. Here's some shots I took of default DCS skins in model viewer and they all (along with every other default skin and custom ones I've loaded) display the problem... 1 - Australian 75th Squadron : has BORT numbers 2 - Blue Angels Jet Team : no BORT numbers 3 - VMFA-122 high visibility: no BORT numbers and text over area This is very odd and I guess it could be something to do with the decal...or is there a reflection file for this BORT decal area? The weird thing is the other decal positions don't display this box so the empty.dds is working properly but it's like this box is somehow hardcoded but I can't find a thing...very strange...

Hi all, I've noticed something odd with the Hornet that I haven't been able to remove. On the outside of the right front gear door (where the F18C_BORT_NUMBER_STV_aus_R_* displays it's numerals - right on the plane, left on the screenshots) there is a box always there that becomes more noticeable during certain reflection situations. Originally I thought it was something in the F18C_1_DIFF_RoughMet.dds but I examined that and there's nothing there to cause the box. Even stranger, the box only appears on the outer right front gear door but not the left door! I checked out all the DCS default F18C skins in Model Viewer and they ALL have this box. I've attached 3 pix, the 1st 2 taken in Model Viewer and the reflection file taken in Gimp to illustrate. The first 2 show the box is on the right but not left with different Model Viewer sun positions. The last is the position in the reflection file that displays these 2 doors and you can see there's nothing there to cause this. I'm sure this has to be a specular related issue in a reflection file somewhere, but I'm going nuts trying to figure out where this reflection is coming from. I've just examined all the files in ../DCS World/Mods/aircraft/FA-18C/FA18-C.zip and there's nothing in there to be causing this I could find. Does anyone have any idea why this decal box is always present and what file this lives in? I've been working on it for over 2 days and am stuck :-) Thanks! Dennis ****** This one shows the box on the right front gear door outside: This one shows the left outside gear door in a similar reflection and that there's no box... This one shows the doors on the reflection file and that there's nothing there that would cause this...

For the first time in my DCS experience I'm definitely all in for a pre-order. I only fly the Su33 & Hornet so the fact that the Kuznetsov is also getting a facelift is a great bonus. I've been into carrier ops my whole life and when the Kuznetsov & Su33 was added way back in Flanker 2.0 I was in heaven. Of course, I also wanted to experience the thrill of a catapult launch so when the Hornet was released...that was amazing. But after watching the vid mentioned earlier in this thread with actual deck crew animations, I'm totally knocked out! This is Amazing 2.0 :thumbup:

Nevermind. I found the upload button. I was looking at the User Files Download page without being logged in

Nevermind. I found the upload button. I was looking at the User Files Download page without being logged in :doh:

Been around since the Flanker DOS days, but always SP. I remember those DOS days well...I didn't care the graphics were not much more than colored in wire frames, the accuracy of the instruments, flight model and the mission recorder blew me away. Then I moved onto Lock On, Flaming Cliffs, FC3 and now DCS. Good times :thumbup:

Hi all, I've been working on a new skin for the Hornet based on the LSU Tigers football team uniform and am just about done. I've never uploaded anything to user files before and after searching for an hour or so can't find any help or guide. Could someone tell me how I'd go about uploading this new skin so it appears in User Files? Thanks! Dennis

Hi all, I've been working on a new skin for the Hornet based on the LSU Tigers football team uniform and am just about done. I've never uploaded anything to user files before and after searching for an hour or so can't find any help or guide. Could someone tell me how I'd go about uploading this new skin so it appears in User Files? Thanks! Dennis

Great news! Thanks again Chuck as always. Could you please let those of us who keep a hardcopy version of your manual know which chapters this new update changes so we can keep up to date. Thanks!

Don't see why not...though without the Kuznetsov ski jump you might need to start your takeoff run at the far end of the stern :smilewink:

Hi all, I have several keyboard commands I press at the beginning of each mission. For example when flying the Su33, I always start a mission with "LShft F10 NumEnt Num5". I noticed in the ME I could write a lua script that is attached to waypoint 0 by selecting "Advanced Waypoint Actions" and choosing "Perform Command" - "Run Script". Is it possible to write a script that handles my startup keyboard commands so I don't have to manually do them at the start of each mission? I've been researching lua scripting and can't seem to find anything that shows how to do this...and many topics that say it isn't possible. I figured this forum was the best place to ask and if anyone had figured out how to do this, I would find them here :smilewink: Thanks!

Thanks for the explanation, that makes sense :thumbup: Also found a page in Chuck's Guide that shows 127.5Mhz is in the AM only range which explains why in the mission editor if the Stennis is at 127.5 it must also be set to AM. Just for fun changed the Stennis to 156Mhz FM in the mission editor and ran the same mission. I changed comm1 to manual mode, punched in 156000 FM and was able to communicate with the Stennis over FM just fine :smilewink: Still bizarre that there are so many old threads saying the Stennis must be contacted at 127.5 FM https://forums.eagle.ru/showthread.php?t=211200 https://forums.eagle.ru/showthread.php?t=208504 Oh well...thanks to all who responded...I learned a lot I didn't know about Hornet radio comms ;)

Got it working, which is great! Though it doesn't make much sense :huh: Decided it would be wise to open one of the DCS provided missions and see if I had the same problem there compared with the missions I created myself. Opened the "FA-18C/Missions/QuickStart/Caucasus FA-18C Case I Carrier" mission in the mission editor. Gave it a try and I was finally able to communicate with the Stennis! Changed the start time to 11pm and gave it another go and after accepting my inbound request the lights came on! To learn why the Stennis comms/lights in my missions weren't working and this one was, I went through all the details between my mission and this quickstart mission and found 1 big difference. In the mission editor, the properly working mission had the Stennis comm set to 127.5Mhz AM not FM. Tested this by changing the Stennis setting in the mission editor to FM and it wouldn't answer. Changed it back to AM and it consistently worked. Went to my mission that wasn't working and changed the Stennis to AM in the mission editor and it now also worked. Went back and reviewed the latest version of Chuck's Hornet Guide and saw that his Case III Recovery tutorial also was setting the Stennis to AM in the mission editor (as shown on pg 316) - a small but apparently huge thing I originally had wrong :doh: I'm very happy to have it working, but this doesn't make sense because everything I read researching this on the forum said the Stennis was 127.5Mhz FM not AM. Strange that setting the Stennis to AM in the mission editor, but setting my comm1 to 127500 FM in the Hornet is what works. I'm just happy I have it working, but it would be very informative if anyone could explain why this works :smilewink:

^ Not that I've noticed.

I've done that...set it to the default 127.5Mhz FM in mission editor...no joy. I'm also able to contact airfields successfully by manually setting comm1 and comm2 during the flight. Everything works but the Stennis...there's definitely something wrong here.

Easy comms off. Have tried setting and sending 127.5 FM from comm 1 in manual mode (as in Chuck's guide). Also tried manually setting in comm 2 just for fun. Have tried pre-setting them to comm1 channel 1 and comm2 channel 1 in the mission editor. Have tried calling with both RAlt-\ and RCtl-\. Even tried with the Stennis both activating TACN and ILCS in the mission editor as it's first actions and not. Tried while on final approach with both gear and hook down. Tried from over 10nm's out. Seriously I've tried everything I can think of and the Stennis doesn't respond to any of my calls so obviously doesn't light up. As I mentioned the only time I can communicate and get an answer from the Stennis is when I'm sitting on the deck :helpsmilie:

So I set up a night landing mission on the Stennis and even though I'm following the Case III landing guide on Chuck's Hornet manual (beginning with calling the ship and requesting inbound triggering the Stennis to light up the deck), the Stennis won't light up. I've tried all sorts of variations on this theme (inbound close to the boat, gear & hook down...flying directly over the boat, etc) and haven't been able to get the Stennis to light up once. Also can't get the Stennis to reply to any of my contact requests...except, when I'm sitting on the deck awaiting takeoff :smilewink: Is anyone else having the same problem with the Stennis?

Food for thought. I do find it interesting though that waypoint elevation is considered critical enough info on the Su25/27/33 that it is both displayed on the HUD and integrated into the ADI (description from the DCS Su33 manual): Attitude Direction Indicator The Attitude Direction Indicator (ADI) shows the current angles of pitch and aircraft roll. In the lower part of the indicator is a yaw slip indicator. Changing the rudder position eliminates slipping, so try to have the indicator in the central position. On the front portion of the indicator are the required bank and pitch indicators to reach the next waypoint. When both yellow bars are in the central position,the aircraft is following the correct route.