Jump to content

Recommended Posts

Posted
On 2/10/2024 at 6:49 AM, Raisuli said:

Can take off once; the second time I take off I have no flight controls.

It was reported some time ago. You should have the controls back in the air though, right?

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted
5 hours ago, draconus said:

It was reported some time ago. You should have the controls back in the air though, right?

Nope.  At least not as long as it takes to hit the water after going into a nice ballistic arc with only flaps and some rudder to manage it.  Took off from 59, landed on 59, took off again, same problem.  59 is now retired and has been replaced with a different carrier.  My gut is it's not likely to come out of mothballs in my lifetime.

Incidentally if you run up to AB, then back down to mil salute gets you off the boat.  On non-SC carriers all you need is mil.  Still need AB to get off the Kuz, though.  At least if you want to keep flying after the deck ends.

  • Like 1
Posted

Try doing a full Repair, when weird stuff like this comes up that nobody else reports it’s a good practice. Updates don’t always go right for reasons….

  • Like 1
  • 2 weeks later...
Posted
20 minutes ago, toni said:

can you shoot via the Request Launch comm menu ?

No, this is for the supercarrier deck crew to get into launch positions.

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted
1 minute ago, toni said:

thanks, so via keyboard I gues

Yes, for non-supercarrier launch you just press Cat Launch/Salute bind (default LShift+U).

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

  • 2 weeks later...
Posted

This the supercarrier at 16x Anisotropic filtering:

j1yUE6f.png

And the same at 0x Anisotropic filtering:

IQTARZu.png

The catapaults and other textures smear but the landing lines stay crisp.

The same can't be said for the forrestal at 0x anisotropic filtering:

mRLjxnT.png

The white landing area lines smear and become invisible ... or should I say even worse than normal. Given that anisotropic filtering can cause stuttering in VR, can you please do the same as ED is doing with the supercarrier module to keep the landing lines visible?

 

  • Like 3
Posted
7 hours ago, MPK said:

0x anisotropic filtering

AF 16x is very cheap and looks horrible at 0x. Why would anyone use it?

  • Like 2

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted (edited)
17 hours ago, draconus said:

Why would anyone use it?

Literally at the end of his post:

On 3/10/2024 at 1:32 PM, MPK said:

Given that anisotropic filtering can cause stuttering in VR

 

REQUEST Make the mules/forklifts visible on the mission editor view so users can avoid them when placing their own statics.

Edited by Nealius
  • Like 3
Posted
5 hours ago, Nealius said:

REQUEST Make the mules/forklifts visible on the mission editor view so users can avoid them when placing their own statics.

Alternatively, I think I'd rather have them just removed entirely so that players can set up the deck as they desire without worrying about them at all.

We have the units so we can place them ourselves and the ability to make templates with them, but there isn't a way to remove the ones that are already there.

  • Like 8

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
On 3/11/2024 at 12:55 AM, Nealius said:

Literally at the end of his post:

 

REQUEST Make the mules/forklifts visible on the mission editor view so users can avoid them when placing their own statics.

 

Why does AF cause stuttering in VR should be the real question. AF these days is basically a fixed 100% setting that devs should just plan on being there. What’s wrong with the VR implimentation?

  • Like 1
  • 3 months later...
Posted
On 3/10/2024 at 5:32 AM, MPK said:

This the supercarrier at 16x Anisotropic filtering:

j1yUE6f.png

And the same at 0x Anisotropic filtering:

IQTARZu.png

The catapaults and other textures smear but the landing lines stay crisp.

The same can't be said for the forrestal at 0x anisotropic filtering:

mRLjxnT.png

The white landing area lines smear and become invisible ... or should I say even worse than normal. Given that anisotropic filtering can cause stuttering in VR, can you please do the same as ED is doing with the supercarrier module to keep the landing lines visible?

 

Looks more like a LOD issue.

  • 2 weeks later...
Posted

I don't know if it's a Forrestal issue or global DCS issue, but LA lights don't appear until 0.5nm in night CASE III, making lineup a pain.

  • Like 4
Posted

Is there a fix for the parked aircraft rotating 180's and facing out to sea, instead of facing inwards towards the centreline ?

AMD Ryzen 9 7845HX with Radeon Graphics           3.00 GHz

32 GB RAM

2 TB SSD

RTX 4070 8GB

Windows 11 64 bit

  • 3 months later...
Posted

It looks like a couple updates back broke the LSO position - it's no longer accessible despite still being defined in the .lua.

  • 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
8 hours ago, Northstar98 said:

It looks like a couple updates back broke the LSO position - it's no longer accessible despite still being defined in the .lua.

Have you tried to set "allow LSO" in ME for the carrier or is it only for SC?

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted
21 minutes ago, draconus said:

Have you tried to set "allow LSO" in ME for the carrier or is it only for SC?

That option isn't available for the Forrestal (or any other vessel), only CVNs 71-75.

Though I'm guessing that's the issue as that setting seems to default to off (i.e. disallowed).

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.

  • 4 weeks later...
Posted
On 11/24/2024 at 7:59 AM, Nealius said:

Ball is unusable at night. The amount of bloom is so excessive that it's a massive cyan blob that's impossible to read. 

Always has been. The bloom scourge has been there since 2.5.

  • Like 1
Posted
10 hours ago, Nealius said:

It was usable at night the last time I used Forrestal some months ago. 

Oh cripes, has lighting gotten worse again? I haven’t done any night in well over a year.

Posted
On 11/28/2024 at 8:45 AM, RustBelt said:

Oh cripes, has lighting gotten worse again? I haven’t done any night in well over a year.

At least the FLOLS. It's usable in the day but crap at night.

  • Like 1
  • Recently Browsing   0 members

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