Rptd: ItO 90M (France/Sweden) - wrong missile tube colours and markings

[Schindibee 2,862]

# I have:

• Restarted the game: yes

• Cleared the cache: yes

• Checked game integrity: yes

• Disabled custom content: yes

•  

# Game version

My game version: (2.13.0.53)

 

# Platform

Windows10 64

 

# Description

The ItO 90M's missile tubes are in the game painted in a much too light olive drab and show blue marker bands. Those blue bands are standard NATO markings for inert weaponry or training weapons, whereas live ammo would be marked with yellow bands.

 

# Steps to reproduce the issue

1. select vehicles in hangar

2. observe colours/markings of missile tub

3. compare to real live photos of the vehicle

 

# Additional Information

Spoiler

Various images of Crotale NG equipped vehicles with live missiles, marked with yellow warning bands:

 

Note: Google picture search using either ItO 90m or Crotale NG as search term yields a lot of pictures documenting the correct missile colours.

 

https://www.valka.cz/FIN-ItO-90-t32198

https://www.armedconflicts.com/FIN-ItO-90-t32198

 

https://www.valka.cz/FIN-ItO-90-t32198

 

https://www.valka.cz/FIN-ItO-90-t32198

 

Source: Finnish army / https://weaponsystems.net/system/425-ItO+90

 

 

https://sputniknews.com/20150629/1023975354.html

 

The following photo shows the vehicle at an exposition, armed with inert/training missiles marked with blue bands:

Source: Tom Raftery / https://weaponsystems.net/system/425-ItO+90

 

 

And finally the missile tubes as depicted currently in the game (note too bright base colour of tubes and wrong blue bands):

 

 

 

Note: many more examples of both live and training/nert missile tubes can be found by using google picture seacrh with search terms "ItO 90M" or "crotale NG"

 

# Affected vehicles

• ItO 90M (France) https://wiki.warthunder.com/ItO_90M_(France)

• ItO 90M (Sweden) https://wiki.warthunder.com/ItO_90M

 

# Files

You must attach these files:

• Screenshots taken using the in-game functionality [Windows, Linux, Mac]    - see above

• Replay or link to server replay (.wrpl or URL) with timestamp [All platforms] - n/a (not relevant as issue can be observed directly in hangar)

• Client log (.clog) [Windows, Linux, Mac] - see following message

• DirectX diagnostic file (dxdiag) [Windows]  - not possible because of software issue (dxdiag not working because of winspool.drv related issue I'm fighting to resolve...)

   

inachis

[Schindibee 2,862]

2022_01_03_10_38_14__8456.clog

[KnightoftheAbyss 3,387]

waiting for reference sources from Schindibee.

[Schindibee 2,862]

Thank you! I've added links to the picture sources, hope this is enough as "reference"...

[KnightoftheAbyss 3,387]

Thanks mate.  I will process this tomorrow for you.  It's getting late here now.

 

[Vonarian 2,888]

Hi, @Schindibee!
For winspool.drv one, please do the following: 

1. Step 1
   Power on or restart your PC. Hold down the "F8" key while the computer is booting. This action provides you with an Advanced Boot Options screen.
2. Step 2
   Press the "Down-Arrow" key once to highlight "Safe Mode" and press "Enter." Allow Windows to load in safe mode.
3. Step 3
   Open a Run dialog by holding "Windows" + "R" consecutively. Type "System32" in its open field, and then press your "Enter" key. This simply opens an Explorer window that displays the contents of the Windows System32 folder.
4. Step 4
   Type "Winspool" in the "Search System32" field, which is located at the top right corner of the window. This will display the Winspool.drv file if it is installed on your system.
5. Step 5
   Right-click the "Winspool.drv" file and click "Rename." Change ".drv" extenstion to the ".bak" extension so that the new file name is "Winspool.bak." If you get a "Requires TrustedInstaller" error, you will need to take ownership of the file.
6. Step 6
   Click "Start." Type "Com Prompt" in Search. Right-click "Command Prompt" and click "Run as Administrator."
7. Step 7
   Type "SFC /Scanfile=C:\Windows\System32\Winspool.drv" in your prompt and press "Enter." This action starts the System File Checker. Since you may not have the file, the utility will see that the "Winspool.drv" file is not in the System32 directory and will create a new one automatically.
8. Step 8
   Restart your computer once you see "…found corrupt files and successfully repaired." You have reinstalled Winspool.drv.

Note: Alternative way for switching to safe mode is the following:

1. Hold "Win" + "R"
2. Type "msconfig" in text box
3. Run the application and go to "Boot" tab
4. Check "Safe Boot" at bottom left.

[KnightoftheAbyss 3,387]

Hi mate,

            Sorry this took longer than it should.  I started it and then got distracted with another issue.

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.

 

KotA