Jump to content

Recommended Posts

Posted

Dear all,

because of the sheer size and scope of this update, we want to offer a specific USS Forrestal Feedback thread: please report your finding and bugs or any related issues concerning the CV-59 Forrestal in this thread. Thank you!

 

HhusEjC.jpg

 

  • Like 8
  • Thanks 1

Heatblur Simulations

 

Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage.

 

http://www.heatblur.com/

 

https://www.facebook.com/heatblur/

Posted

Beautiful model of the ship! 👍  Just curious though, why throw in a Tilly for that time period and then clutter up the possible parking places for it with static (immovable) fork lifts, tugs and huffers?? Where do your artists expect us mission builders to put it?

  • Like 1

[sIGPIC][/sIGPIC]

Posted
4 minutes ago, AG-51_Razor said:

Beautiful model of the ship! 👍  Just curious though, why throw in a Tilly for that time period and then clutter up the possible parking places for it with static (immovable) fork lifts, tugs and huffers?? Where do your artists expect us mission builders to put it?

Hey!

Actually- the tilly we added now is the wrong model (just painted yellow) temporarily. The changelog should have reflected. The real NS-60 Tilly will be added in the next update, and then it will be placeable (or default near the island). So to answer your question; the tugs and forklifts currently clutter that area because we are waiting to add the proper NS60. 🙂

  • Like 15

Nicholas Dackard

 

Founder & Lead Artist

Heatblur Simulations

 

https://www.facebook.com/heatblur/

Posted

Hello,

Seems that the Forrestal is not compatible with the Historic Filter feature of the Mission Editor. This carrier should be allowed historically for the period 1955 – 1998.

Great model, thanks a lot for leaving it free even for people that hasnt purchased the Tomcat yet 👍

Eduardo

  • Like 7

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted (edited)

It is a beautiful ship, but the worn-out paint of the landing area markers makes it very hard to line up properly in VR, even harder than with the other carriers.
But that has always been a problem: before the SC days, I used a custom livery that a friend of mine made for the default Stennis, which made the landing area a lot better visible.
Did the real Forrestal also have the green/amber/red line-up lights at the back, or was that implemented later on? If it had, I hope something can be worked out with ED to give the Forrestal even more utility. Currently, the SC voices are used and also the LSO mechanics which means even on the Forrestal the LSO will report an incoming F-14 as "you're slow" even when the plane is exactly on-speed or even a little fast. It would be nice to see this corrected at some point 🙂 

Edited by Raven (Elysian Angel)
typo
  • Like 6
Spoiler

Ryzen 9 5900X | 64GB G.Skill TridentZ 3600 | Asus ProArt RTX 4080 Super | ASUS ROG Strix X570-E GAMING | Samsung 990Pro 2TB + 960Pro 1TB NMVe | VR: Varjo Aero
Pro Flight Trainer Puma | VIRPIL MT-50CM2 grip on VPForce Rhino with Z-curve extension | Virpil CM3 throttle | Virpil CP2 + 3 | FSSB R3L | VPC Rotor TCS Plus base with SharKa-50 grip | Everything mounted on Monstertech MFC-1 | TPR rudder pedals

OpenXR | PD 1.0 | 100% render resolution | DCS graphics settings

 

Posted (edited)

I've only got a few minor nitpicks, the Forrestal really is a work of art, easily on par or even surpassing the SC module ships (especially the Kuznetsov), so it's really difficult to find fault with it. HB have done a fantastic job :thumbup:

 

Phalanx CIWS

Firstly, the barrels are a bit on the long side.

Forrestal is currently depicted with Phalanx Block 1 (accurate for the Forrestal for 1990 - 1993). EDIT: This is actually incorrect, images from 1989 through to 1992 show Phalanx Block 0, meaning the current Phalanx is incorrect (the difference between Block 0 and 1 is not a trivial one, or at least, it wouldn't be if DCS modelled them properly). But both Phalanx Block 0 and Block 1 have the shorter 1520 mm gun, as opposed to the Block 1B's 2000 mm gun.

The muzzle is also incorrect.

hgnA4RI.png

Mk-15-CIWS-027.jpg

Mk-15-CIWS-030.jpg

Note the shorter magazine (more-or-less flush with the gun mount), shorter barrels and the muzzle.

 

Additionally this Phalanx seems to not be far out enough.

ewmvkm0.png

fPIjzrh.jpg

Also note the barrel.

 

IFLOLS Camera:

The camera on the FLOLS is facing backwards:

jbx52iB.png

cksYdO3.png

 

AN/SPS-49

The AN/SPS-49 has vertical elements that are all the same size, making the antenna look rectangular. From images I've seen the 2 closest to each edge of the antenna should be shorter, making the antenna look more elliptical:

sOjutFG.png

an-sps49-nrl.jpg&f=1&nofb=1

Speaking of which, like all other ships with these RADARs, the AN/SPS-48C and AN/SPS-49(V)5 NTU (fairly sure those are the variants for our post SLEP Forrestal), are undefined:

GT.Sensors = {  OPTIC = {"long-range naval optics", "long-range naval LLTV"},
                RADAR = {
                    "seasparrow tr",
                    "carrier search radar",
                },
            };

"sea sparrow tr" refers to the Mk95 illuminators (in DCS these have searching capability, whereas IRL, they just used to provide CW illumination, with acquisition handled by the AN/SPS-48 and/or -49. The Mk95 illuminators aren't animated either. Of course Forrestal suffers from the same RADAR modelling and limitations as every other ship in DCS.

"carrier search radar" is a generic surface-search RADAR (common to all aircraft carriers), used as a stand-in for the AN/SPS-64(V)9 and AN/SPS-67(V)1.

 

Also to note (though not sure if it's planned), the Forrestal is the only aircraft carrier in DCS to not have a hangar modelled, despite, rather curiously, the elevators being animated.

 

Other than these very minor nitpicks, the ship is fantastic, easily on par (or even surpassing) the Supercarrier :thumbup:

On 10/20/2021 at 6:39 PM, Cobra847 said:

Hey!

Actually- the tilly we added now is the wrong model (just painted yellow) temporarily. The changelog should have reflected. The real NS-60 Tilly will be added in the next update, and then it will be placeable (or default near the island). So to answer your question; the tugs and forklifts currently clutter that area because we are waiting to add the proper NS60. 🙂

Great to hear!

Personally, it would be better if the area was left empty, and leave it up to mission editors to populate as they see fit.

Edited by Northstar98
Evidence actually suggests that Forrestal never received Phalanx Block 1, only Block 0.
  • Like 8
  • Thanks 2

Modules I own: F-14A/B, F-4E, Mi-24P, AJS 37, AV-8B N/A, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk.

Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas.

System:

GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, NVIDIA GeForce RTX 4070S FE, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV.

Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.

Posted (edited)

To HB team, I posted here a detail about weapons, sensors, systems and airwings of Forrestal Class (Some detail need detail a little). From all guns Mk42 5in/54 carriers on 55 to late versions.

 

Edited by Silver_Dragon
  • Like 1

For Work/Gaming: 28" Philips 246E Monitor - Ryzen 7 1800X - 32 GB DDR4 - nVidia RTX1080 - SSD 860 EVO 1 TB / 860 QVO 1 TB / 860 QVO 2 TB - Win10 Pro - TM HOTAS Warthog / TPR / MDF

Posted

IFOLS is too bright, I can hardly see the meatball with gamma at default setting, because the green lights are blinding. Can even see it from the side of the ship way outside the grove on the downwind leg.

  • Like 1

DCS F/A-18C :sorcerer:

Posted

Does the waist catapults work? I can’t seem to get linked on Cat 3. 1 and 2 work. Haven’t tried 4 yet.

4 works. However, I pressed U again to cancel to ready the cat in F2 view. I can’t get back into cockpit by pressing F1. Actually all view keys are unresponsive. I can move throttle and hear engines rev up, rudders move, stabs move. Views are broken somehow.

Hmm, weird, I let it sit a while and now functional again. Just went back to cat 3 and still not functional.

Sent from my iPhone using Tapatalk Pro

Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer

Posted

The ship looks awesome, on par with the payware carriers, in some areas even better. I love the overall "dirtiness" . The IFLOS is a nightmare though....

  • Like 3

i5-8600k @4.9Ghz, 2080ti , 32GB@2666Mhz, 512GB SSD

Posted

This carrier looks fantastic. Amazing job. Love the color palette that was used. The deck and overall surfaces look so realistic, at least to my eyes! 

After placing a few static deck crew around the joint, this thing gives the supercarrier a run for its money!

Only small thing I noticed was the ship's props not turning whilst underway, but otherwise, great job and thank you very much!!

newfor.png

  • Like 4

I7 4790k EVGA 1080ti FTW 16gb Corsair Dominator Acer Predator 2k 165hz Thrustmaster Pedals & Warthog TrackIr5

Posted
1 hour ago, Eagle7907 said:

I can’t seem to get linked on Cat 3

It worked for me, but you have to make sure you’re more or less in the correct spot, same as with the default Stennis.

Spoiler

Ryzen 9 5900X | 64GB G.Skill TridentZ 3600 | Asus ProArt RTX 4080 Super | ASUS ROG Strix X570-E GAMING | Samsung 990Pro 2TB + 960Pro 1TB NMVe | VR: Varjo Aero
Pro Flight Trainer Puma | VIRPIL MT-50CM2 grip on VPForce Rhino with Z-curve extension | Virpil CM3 throttle | Virpil CP2 + 3 | FSSB R3L | VPC Rotor TCS Plus base with SharKa-50 grip | Everything mounted on Monstertech MFC-1 | TPR rudder pedals

OpenXR | PD 1.0 | 100% render resolution | DCS graphics settings

 

Posted
2 hours ago, Rudel_chw said:

Hello,

Seems that the Forrestal is not compatible with the Historic Filter feature of the Mission Editor. This carrier should be allowed historically for the period 1955 – 1998.

Great model, thanks a lot for leaving it free even for people that hasnt purchased the Tomcat yet 👍

Eduardo

Agreed! Although, she was decommissioned in 1993. So 1955-1993.

  • Like 1

DO it or Don't, but don't cry about it. Real men don't cry!

Posted

I’ve been stopping just aft of the shuttle. I turn off NWS, kneel down the jet, then press U. Nothing happened. On the other cats, you can see them steam up, but I couldn’t get cat 3 to work. I’ll try again later.


Sent from my iPhone using Tapatalk Pro

Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer

Posted (edited)
1 hour ago, Wizard_03 said:

IFOLS is too bright, I can hardly see the meatball with gamma at default setting, because the green lights are blinding. Can even see it from the side of the ship way outside the grove on the downwind leg.

You can also see it from the bow, doesn't look like LOS to the lights are modelled, it's especially noticeable from further away.

Edited by Northstar98
  • Like 1

Modules I own: F-14A/B, F-4E, Mi-24P, AJS 37, AV-8B N/A, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk.

Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas.

System:

GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, NVIDIA GeForce RTX 4070S FE, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV.

Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.

Posted

The IFLOS has light bloom when looking back at it from the front of the boat. the bloom is pretty bad until at 3/4 of a mile from behind the boat

  • Like 1
Posted (edited)

First, a huge thanks to HB. This is a fantastic and very generous addition to DCS. The carrier looks beautiful.

 

What I have found is that in VR, the datum lights and the ball are severely over-blooming. They even spill over when viewed from the bow:

Screen_211020_212815.png

May I also make some suggestions in regards to the spawn positions? It seems that the Forrestal has taken the same approach as the Stennis and the SCs with the first flight at mission start spawning at the center of the deck (these spawn points only work at mission time 0 and wont be available into the mission):

Screen_211020_223519.jpg

This setup often causes issues for me, as this blocks access to the catapults. Especially with AI this often leads to problems and stuck aircraft. May I suggest to move this spawn positions in front of the island as so?

 

Screen_211020_223734.jpg

As you can see, there should be sufficient space available for that setup and it frees all aircraft to taxi. Personally, I would also re-arrange the numbering to give priority to the deck edge parkings, but that is just my preference.

May I also suggest that you define additional "overflow" spawn positions at the stern of the ship?

Screen_211020_224157.jpg

I know this will block the landing area, but don't think this is a problem. If numbered positions 13-20, they would only be used if the first 12 spawn positions are occupied. In single player the mission designer can coordinate landing aircraft if he wants to use these "overflow" positions. In public multiplayer I think it is extremely rare that more than 12 people will spawn simultaneously on a carrier. Organized multiplayer groups that might want to spawn with more than 12 players simultaneously will be able to coordinate launch and recovery operations.

Edited by MBot
  • Like 4
Posted (edited)

found that a F-14A AI Landing looks to Overshoot end of deck, but it doesn't fall and after some height things, it goes around to park
( in custom mission specifically to see all new carrier )

 

 

Screen_211020_154554.png

Edited by Lodkins
  • Like 1
Posted (edited)

Really nice work on the modeling! Fantastic attention to detail. You can see the love that went into this. Thank you! 
 

I’m finding it very hard to line up accurately in VR. It’s not a resolution issue. I can see the shape of the deck clearly, but I can’t see any markings on the deck until over the fantail. I can adjust the gamma to correct, but then the rest of the world is washed out. It might very well be just me and my setup, but I’d thought I’d report it for corroboration or elimination due to user failure. 

Edited by Palmetto 1-1
  • Like 1
Posted
1 hour ago, MBot said:

First, a huge thanks to HB. This is a fantastic and very generous addition to DCS. The carrier looks beautiful.

 

What I have found is that in VR, the datum lights and the ball are severely over-blooming. They even spill over when viewed from the bow:

Screen_211020_212815.png

May I also make some suggestions in regards to the spawn positions? It seems that the Forrestal has taken the same approach as the Stennis and the SCs with the first flight at mission start spawning at the center of the deck (these spawn points only work at mission time 0 and wont be available into the mission):

Screen_211020_223519.jpg

This setup often causes issues for me, as this blocks access to the catapults. Especially with AI this often leads to problems and stuck aircraft. May I suggest to move this spawn positions in front of the island as so?

 

Screen_211020_223734.jpg

As you can see, there should be sufficient space available for that setup and it frees all aircraft to taxi. Personally, I would also re-arrange the numbering to give priority to the deck edge parkings, but that is just my preference.

May I also suggest that you define additional "overflow" spawn positions at the stern of the ship?

Screen_211020_224157.jpg

I know this will block the landing area, but don't think this is a problem. If numbered positions 13-20, they would only be used if the first 12 spawn positions are occupied. In single player the mission designer can coordinate landing aircraft if he wants to use these "overflow" positions. In public multiplayer I think it is extremely rare that more than 12 people will spawn simultaneously on a carrier. Organized multiplayer groups that might want to spawn with more than 12 players simultaneously will be able to coordinate launch and recovery operations.

 

You wouldn't park F-14s there, that in front of the island is called the "Helo Hole" and the helicopters park there with folded blades... Also, more towards the aft of the island from the Helo Hole is where the E-2Cs would be parked.

 

Generally speaking of course, at start of flight operations... Often on a full flight deck you would see F-14s needed to launch on that cycle being parked right over the fantail right along the landing deck.

  • Like 2
Posted
6 minutes ago, Baz000 said:

You wouldn't park F-14s there, that in front of the island is called the "Helo Hole" and the helicopters park there with folded blades... Also, more towards the aft of the island from the Helo Hole is where the E-2Cs would be parked.

 

In DCS these are just spawn positions not tied to specific aircraft types. 

Still...

flight-deck-crewmen-service-fighter-squa

  • Like 5
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...