Jump to content

Recommended Posts

Posted

My apologies if this has come up before, but a thread search did not return any hits, and I don't want to manually sort through a 113 page thread.

 

Bug Report:

 

Type: Mission Scripting

 

Affected Mission: A-10A The Valley 6A

 

Problem: Victory fails to trigger despite destroying the objective (T-80 Platoon with T-80s #21-23) described in the briefing.

 

Cause: There is an additional, undocumented, victory trigger in this mission: Destroy T-80 HQ Group.

 

Recommendation: Amend mission briefing so that the player understands that he must destroy both the T-80 Platoon group and the T-80 HQ group, OR remove Destroy T-80 HQ Group victory trigger.

Posted

I tried the Su-27 with an ECM pod in my mission and the ECM light in the cockpit never turns on, IDK if its not working or if the pod just doesnt work currently.

 

and also its really hard to see and read the trim lights and the autopilot lights in the cockpit, IDK if thats intended

 

version 1.2.4

 

track added,

ECM.trk

Posted

FINALLY the gun appears to be fixed for the F-15. Been waiting for that fix since FC3 came out. Short bursts incapacitate if not outright kill fighters now, where before it took half the darn belt to down something. Can anyone confirm this was officially fixed or am I getting luck / imagining it?

Posted (edited)

I have the same ECM issue. No green light signal on cockpit panel. Maybe in real cockpit there are no such green light?

 

Also no afterburner green lights when this engine mode is on.

 

Also no letters when canopy is open, only a red light inside the warning box but no letters at allю

 

Also TWS 2 mode on Mig-29S is off HUD side.

Edited by Esac_mirmidon

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Posted (edited)

SU27 in Ver 1.2.4 Air to Ground CCRP mode not working correctly..weapons release as soon as the pickle button is pressed.

 

After flying the Pipper to the target and pressing and holding the pickle button, weapons release immediately and impact grossly short. The usual process of the time to release cue and "Fly the tail to the director circle" just doesn't happen. As soon as press and hold the pickle button the Time to go arrow races to the bottom of the TTG scale.

 

CCIP works just fine.

 

MIG29 CCRP works as advertised so its an SU27 issue

Edited by IvanK
Posted (edited)

FC3 1.2.4, A10A 6DOF Cockpit;

 

When engaging the speed break the course setter knobs move under the compass course setter. :joystick:

 

So there is no Speed break indicator either anymore?

Edited by Mastiff

"any failure you meet, is never a defeat; merely a set up for a greater come back",  W Forbes.

"Success is not final, failure is not fatal, it is the courage to continue that counts",
"He who never changes his mind, never changes anything," Winston Churchill.

MSI z690 MPG DDR4 || i9-14900k|| ddr4-128gb PC3200 |zotac RTX 5080|Game max 1300w|Win11| |turtle beach elite pro 5.1|| ViRpiL,T50cm2||MFG Crosswinds|| VT50CM-plus rotor Throttle || G10 RGB EVGA Keyboard/MouseLogitech || PiMax Crystal VR || 32 Asus||

Posted (edited)

FC3 1.2.4 A10A

 

Weapons release mode does not work.

 

Can not set up pickle salvo, time, or ripples.

Edited by Mastiff

"any failure you meet, is never a defeat; merely a set up for a greater come back",  W Forbes.

"Success is not final, failure is not fatal, it is the courage to continue that counts",
"He who never changes his mind, never changes anything," Winston Churchill.

MSI z690 MPG DDR4 || i9-14900k|| ddr4-128gb PC3200 |zotac RTX 5080|Game max 1300w|Win11| |turtle beach elite pro 5.1|| ViRpiL,T50cm2||MFG Crosswinds|| VT50CM-plus rotor Throttle || G10 RGB EVGA Keyboard/MouseLogitech || PiMax Crystal VR || 32 Asus||

Posted
SU27 in Ver 1.2.4 Air to Ground CCRP mode not working correctly..weapons release as soon as the pickle button is pressed.

 

After flying the Pipper to the target and pressing and holding the pickle button, weapons release immediately and impact grossly short. The usual process of the time to release cue and "Fly the tail to the director circle" just doesn't happen. As soon as press and hold the pickle button the Time to go arrow races to the bottom of the TTG scale.

 

CCIP works just fine.

 

MIG29 CCRP works as advertised so its an SU27 issue

 

Known issue and has been reported. Thanks a bunch.

Dusty Rhodes

 

Play HARD, Play FAIR, Play TO WIN

 

Win 7 Professional 64 Bit / Intel i7 4790 Devils Canyon, 4.0 GIG /ASUS Maximus VII Formula Motherboard/ ASUS GTX 1080 8 GB/ 32 Gigs of RAM / Thrustmaster HOTAS Warthog / TrackIR 5 / 2 Cougar MFD's / Saitek Combat Pedals/ DSD Button Box FLT-1

Posted
some of the letters and numbers on the su-27 don't completely fit inside the hud.

 

Don't think this is a bug... can you show a screenshot?

PC specs:

Windows 11 Home | Asus TUF Gaming B850-Plus WiFi | AMD Ryzen 7 9800X3D + LC 360 AIO | MSI RTX 5090 LC 360 AIO | 55" Samsung Odyssey Gen 2 | 64GB PC5-48000 DDR5 | 1TB M2 SSD for OS | 2TB M2 SSD for DCS | NZXT C1000 Gold ATX 3.1 1000W | TM Cougar Throttle, Floor Mounted MongoosT-50 Grip on TM Cougar board, MFG Crosswind, Track IR

Posted

Anyone's having problems with Comms menu key? I'm not able to get it working in any FC model.

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Posted

Ive noticed that some of the missions in the FC3 mission folder including the instant mission for the SU-27, you cannot kill the AI aircraft, they seem to be invincible, also when the an enemy aim-9, or aim-120 hits you it usually ends up removing your aircraft from existence, or removing every controlling surface from it along with most electronics.

 

Now i understand that a fighter, shouldnt be able to survive a hit from a A2A missile, its just that suddenly being left with no wings, stabilizers and engines looks really goofy.

 

And another thing the sound from the engines no longer cuts out when you go supersonic, and the volume on the RWR can barely be heard when the afterburner is on, even on its highest volume. This is all for the Su-27

missile.trk

missile2.trk

Posted

Engine sounds should not be cut out when supersonic as there is air within fuselage that transfers some of the engine sound no mater what the speed is. Also on my end I can still hear RWR sounds when I have afterburners on, I think you are just not used to more wind noise that really exists in jet and is dominant sound in the cockpit (that's what I heard from RL pilot)

PC specs:

Windows 11 Home | Asus TUF Gaming B850-Plus WiFi | AMD Ryzen 7 9800X3D + LC 360 AIO | MSI RTX 5090 LC 360 AIO | 55" Samsung Odyssey Gen 2 | 64GB PC5-48000 DDR5 | 1TB M2 SSD for OS | 2TB M2 SSD for DCS | NZXT C1000 Gold ATX 3.1 1000W | TM Cougar Throttle, Floor Mounted MongoosT-50 Grip on TM Cougar board, MFG Crosswind, Track IR

Posted
Ive noticed that some of the missions in the FC3 mission folder including the instant mission for the SU-27, you cannot kill the AI aircraft, they seem to be invincible, also when the an enemy aim-9, or aim-120 hits you it usually ends up removing your aircraft from existence, or removing every controlling surface from it along with most electronics.

 

Now i understand that a fighter, shouldnt be able to survive a hit from a A2A missile, its just that suddenly being left with no wings, stabilizers and engines looks really goofy.

 

And another thing the sound from the engines no longer cuts out when you go supersonic, and the volume on the RWR can barely be heard when the afterburner is on, even on its highest volume. This is all for the Su-27

 

You can survive an indirect hit (proximity warhead detonation), this has happened in combat. What you shouldn't survive is a direct hit which will only happen in a fraction of the shots taken.

.

Posted
You can survive an indirect hit (proximity warhead detonation), this has happened in combat. What you shouldn't survive is a direct hit which will only happen in a fraction of the shots taken.

 

well currently it looks like a proximity hit leaves you with no ailerons and a direct hit leaves you without wings and stabilizers

Posted (edited)

Here are some few bugs from 1.2.4 ; I was flying the Su-27 :

 

1- If I open the canopy while flying : I hear a specific scratch noise and it does not appear in external view (correct) but I still see it in the cockpit view (blocked open position).

Edit : is ok with Su-25 or any other FC3 plane ; only concerns the Su-27.

 

2- At full night, I don't see any flare light in my rearview mirrors (even if it lights the rear of my plane) actually, I see some "small grey clouds" instead of bright balls of fire like with Mig-29x or Su-33.

Edited by Fouga

[sIGPIC][/sIGPIC]

EVAC : French virtual fighter school on DCS-World

Posted (edited)
Small grey clouds sounds like chaff...? Sure you were popping flares?

Yep, I talk about flares ; See and compare below : Su-27 and Su-33.

 

Flare+night+Su-27+1-2-4.jpg Flare+night+Su-33+1-2-4.jpg

Su-27 (upper picture) / Su-33 (lower one)

 

It's like if the flare texture lost color only for the new 6DOF Su-27 cockpit (only by night).

Edited by Fouga

[sIGPIC][/sIGPIC]

EVAC : French virtual fighter school on DCS-World

Posted (edited)
Here are some few bugs from 1.2.4 ; I was flying the Su-27 :

 

1- If I open the canopy while flying : I hear a specific scratch noise and it does not appear in external view (correct) but I still see it in the cockpit view (blocked open position).

Edit : is ok with Su-25 or any other FC3 plane ; only concerns the Su-27.

 

2- At full night, I don't see any flare light in my rearview mirrors (even if it lights the rear of my plane) actually, I see some "small grey clouds" instead of bright balls of fire like with Mig-29x or Su-33.

 

I have confirmed both bugs in latest test builds and reported to ED

Edited by Kuky

PC specs:

Windows 11 Home | Asus TUF Gaming B850-Plus WiFi | AMD Ryzen 7 9800X3D + LC 360 AIO | MSI RTX 5090 LC 360 AIO | 55" Samsung Odyssey Gen 2 | 64GB PC5-48000 DDR5 | 1TB M2 SSD for OS | 2TB M2 SSD for DCS | NZXT C1000 Gold ATX 3.1 1000W | TM Cougar Throttle, Floor Mounted MongoosT-50 Grip on TM Cougar board, MFG Crosswind, Track IR

Posted
Anyone's having problems with Comms menu key? I'm not able to get it working in any FC model.

 

works on mine.

"any failure you meet, is never a defeat; merely a set up for a greater come back",  W Forbes.

"Success is not final, failure is not fatal, it is the courage to continue that counts",
"He who never changes his mind, never changes anything," Winston Churchill.

MSI z690 MPG DDR4 || i9-14900k|| ddr4-128gb PC3200 |zotac RTX 5080|Game max 1300w|Win11| |turtle beach elite pro 5.1|| ViRpiL,T50cm2||MFG Crosswinds|| VT50CM-plus rotor Throttle || G10 RGB EVGA Keyboard/MouseLogitech || PiMax Crystal VR || 32 Asus||

Posted (edited)

FC3 v1.2.4 A10A

 

the HUD is magnified large can not see it properly.

 

Solved its the 6dof neck center mod, causing the hug magnification.

Edited by Mastiff

"any failure you meet, is never a defeat; merely a set up for a greater come back",  W Forbes.

"Success is not final, failure is not fatal, it is the courage to continue that counts",
"He who never changes his mind, never changes anything," Winston Churchill.

MSI z690 MPG DDR4 || i9-14900k|| ddr4-128gb PC3200 |zotac RTX 5080|Game max 1300w|Win11| |turtle beach elite pro 5.1|| ViRpiL,T50cm2||MFG Crosswinds|| VT50CM-plus rotor Throttle || G10 RGB EVGA Keyboard/MouseLogitech || PiMax Crystal VR || 32 Asus||

Posted
the HUD is magnified large can not see it properly.

And heading tape at bottom of HUD is concealed by the protrusion in the middle of the dash (what is that?), which means you cannot see the Waypoint indicator on the heading tape.

 

Also... the A-10A still starts with full left rudder deflection (only tested airborne start Multiplayer in 1.2.4, but was same previously in 1.2.3 for air and ground, so I'm assuming it's still the same in 1.2.4).

"Snipe"

--------------------------------------------------------------------------------

OS => Win7 64-bit Ultimate | MOBO => ASUS M2N-SLI Deluxe | RAM => 8GB | VIDEO CARD => XFX ATI 4850 | CONTROLLER => Saitek X52 | DISPLAY => ASUS 25.5" 1600x1280 | HDD => 150GB WD Raptor (10K RPM)

Posted (edited)

Additional bug(s) relative to the Weapon system Control panel of the Su-27 :

 

3- The Su-27 Weapon system control panel (WCS) does not indicate any information at all ; not at least the GUN / RKT / Bomb mode nor the remaining Gun Ammo.

Su-33 and Mig-29x WCS still indicate that information.

The Su-25 WCP works perfectly with the additional Ripple interval / Qty selectors (as well as the Su-25T one).

 

4- About the Salvo mode, how can we have a feed back about its selection in Su-27 and Su-33 ? I did not notice any modification on the HUD, WCS or the Weapon status panel.

Only the Mig-29x seems to show (on HUD only) if this Salvo mode in engaged.

Edited by Fouga

[sIGPIC][/sIGPIC]

EVAC : French virtual fighter school on DCS-World

Posted

Significant FPS drop in 1.2.4 with the new pits. Seems like I used to be able to fly around in my Su-27 with 40-70 fps no problems. Now with the new cockpit and 1.2.4 I'm down to 18-35. What gives? I know the new cockpits are more detailed and what not but that big of a hit? The biggest hit comes when i turn on cockpit lights, I can be down in the 18-20 range. Here are others like me:

 

http://forums.eagle.ru/showthread.php?p=1739896#post1739896

Intel i7-8700k Coffee Lake@stock

G.Skill TridentZ RGB 32GB (2x16) 3200MHz

ASUS ROG STRIX GTX 3070 Ti

Corsair AX1200i 1200 Watt

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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