Rptd: [2.11.0.71] Mig-21MF (others?) R-3S Pylon renders and overlaps with R-60 Pylon ONLY when R-60 + other weapon configuration is selected.

[armablign 33]

# I have:

• Restarted the game: yes

• Cleared the cache: yes

• Checked game integrity: yes

• Disabled custom content: yes (Re-enabled for screenshot purposes, to illustrate the bug more clearly)

# Game version

My game version: (2.11.0.71)

# Description

The R-3S weapon pylon renders with R-60 Pylon whenever the R-60 missile + Another Weapon configuration is selected. Resulting in both R-3S pylon and R-60 pylon overlapping each other.
When only equipping the R-60 (R-60 4x) loadout, there is no pylon overlapping, and the R-3S pylon does not render. 

# Steps to reproduce the issue

1. Equip R-60 4x loadout for MiG-21MF. Note the length of the 'launch' pylon. (The rail) 

2. Equip any other loadout where there is R-60 2x missiles. (R-60 x2, S-5K x64.    R-60 x2, S-24 x2.     OFAB-250 x2, R-60 x2)

   and note the extra length added to the R-60 Pylon 'launch rail'. This is indeed the R-3S launch rail, as shown with colors below.

# Additional Information

Please note, this problem existed without custom content (Which I provide screenshots for). But for the purpose to illustrate, and show the different pylons, I made a skin that turns the different pylons to solid colors to highlight them better.
Below:

• Blue  - S-24 Launch Rail Pylon 
• Red - R-60 Launch Rail Pylon 
• Green - R-3S Launch Rail Pylon 

Spoiler

S-24 x4 (Only Blue)
 

R-60 x4

PLEASE NOTE:  The Pylon is only RED and shorter in length.

This is the R-60 Missile launch rail.

 

 

R-3S x4 (Only Green) (Longer in length)

This is the R-3S launch rail.

Below: Equipping Loadouts where R-60 x2 + Other Weapon x2. 

Note: The R-3S Launch Rail Pylon (Shown in green) sticks out at the back of the R-60 Pylon (Red). When only R-60 (Red) should be rendering (exist).

Spoiler

 

 

Reminder that the R-60 launch rail is Red.
When equipping the R-60 x2, only the Red pylon should render, not also the R-3S. 

Below: 'Control' screenshots, where I have the color coding skin turned off. As well as, show screenshots on test drive and not just the Hanger screen.

As well as, a screenshot showing the R-3S x2 loadout with another weapon system, showing that it correctly only renders the respective launch rail.

Spoiler

Skin Turned Off:
R-60 x4. 

ONLY R-60 Pylon rendered. (Correct)

Note: Short length of R-60 Pylon.

 

 

R-60 x2 + S-5K x64

R-3S launch rail + R-60 launch rail load. (Wrong)

Note: Extended length. This is the R-3S pylon loading in as well and overlapping.

 

In Game:

R-60 x4 loading correct launch rail pylons.

 

When R-60 + Other Weapon selected.

R-3S launch pylon also loads ontop of R-60 pylon.

(Note the green bit  that sticks out the back, that is the R-3S launch Rail.)

 

 

 

# Affected vehicles

• (German) MiG-21MF

• (Other MiGs-21 Potentially, however I am unable to test that)

# Files

• Client log (.clog) 2021_11_17_16_23_12__16008.clog

• DirectX diagnostic file (dxdiag) DxDiag.txt

[KnightoftheAbyss 3,385]

Hi,

Thanks for the report.

We will investigate, test and get back to you shortly,

Cheers,

Technical Moderation Team

[armablign 33]

Thank you
Glad to hear the report came through.
I hope my post was clear and somewhat easy to follow. Hence why I even made a skin dedicated just to try and highlight the launch rails.

Question , I found another Bug regarding the F2G's model where one of the radiator fins bugs out. Do I wait for this post to be resolved and then post that bug report, or can I make another post?
Asking because I don't want to make multiple reports, as I fear it may look like I am spamming the forum. 

 

[KnightoftheAbyss 3,385]

10 hours ago, armablign said:

Question , I found another Bug regarding the F2G's model where one of the radiator fins bugs out. Do I wait for this post to be resolved and then post that bug report, or can I make another post?
Asking because I don't want to make multiple reports, as I fear it may look like I am spamming the forum. 

Multiple reports will be required.  Reports are largely model based.   So you report an issue for each model.  If multiple models all exhibit the same issue, then it is okay to report all at once.

 

[KnightoftheAbyss 3,385]

Hi.

   I have confirmed this on the German MiG 21.  I am now investigating the others.  This will take some time due to the number involved etc.

 

 

[armablign 33]

Hey.

Thank you for the update and confirmation.
That is alright, sorry for indirectly placing that matter on your shoulders, I would have loved to full investigate the others myself, however I only have access to the German MiG21MF (and 21bis on standby)

If you think it would help
I can, maybe attempt to give you a user made skin (the one used in my report) and try and create .blk files for all and each of the MiG21's that use the same launch rail (I think most to all of them do), and send that over, so that the overlapping geometry for each can be way more clear/visible. 

Edited November 29, 2021 by armablign
Correction of statements, and improved phrasing.

[armablign 33]

I went ahead and added the other MiG21's and their .blk files included in the userskin I made. 
I only did it for the: 21Bis, 21Bis_SAU, 21MF and 21 SMT,
as I think those should be the only ones effected, as they are the only 21's that are able to equip R60s + Other ordinates.

However, I am not able to personally test these for the MiG 23 (and MiG 27?), 
firstly, since I don't have access to them, and also, I do not want to make assumptions as to if this bug extends to the MiG23 and newer.

User Skin File that color highlights the apu_13 (R-3S Rail) , apu_60m (R-60 Rail) and su_apu_68um2 (S-24 Rail)
Mig21 BUG REPORT -armablign.rar

 

I profusely apologies, if it is wrong of me or against forum rules
for me to upload said skin file.
I hope that my intentions are clearly in-order to aid you, if in case this is the case 

[KnightoftheAbyss 3,385]

Thanks for all that.

 

We test this all on the Development Server,(this is what it is really for!).   But access to that server is restricted unless it is a pre update release.

 

Thanks anyway.

 

 

[armablign 33]

Oh! Yea, that makes total sense, I thought you meant testing it with the live/stable release client.
Using the dev server for such, makes total sense!

It is a complete pleasure, I always want to do what ever I can to assist, and assist the community by improving the game wherever possible 

Much appreciated!

[KnightoftheAbyss 3,385]

Hi,  

    I will get to this shortly.  Sorry for the delay.

 

[armablign 33]

Hi,
No problem at all!
I've been on holiday until today, so it didn't cross my mind or bother me one bit.
I don't mind the delay at all so please don't stress about it c:
 

[KnightoftheAbyss 3,385]

Hi
  Thank you for your interest and help improving the game.  

Your information has been forwarded to the Developers for their consideration.  

If there is anything further regarding this report a Technical Moderator will contact you.

Thank you again for your support.