Search the Community
Showing results for tags 'canopy'.
Found 9 results
-
reported Canopy Glass is Flickering During Head/Zoom Movement
razo+r posted a topic in Bugs and Problems
The external part of the glass is flickering. -
There appears to be some sort of visibility bug with the interior canopy glass material FW_190_GLASS_INT. All textures, to include the diffuse, and the roughmet and probably the glass ('14' in the description.lua) will flicker in visibility when head or zoom movement occurs. Here is a video, after I gave each material's diffuse texture a color (seen in the quotations in the description.lua at the end). If you remove the diffuse texture (set it to empty) so you only show the the glass texture ('14') for FW_190_PLEXGLASS_extr, it flickers with its parent material FW_190_GLASS_INT as well. This does not appear to be due to the interior and exterior planes being positionally coincididal (overlapping), as you can still make out the two if you move the camera inside the glass pane. The glass hue texture (14), which is used on both inside and outside materials: The FW_190_GLASS_INT in red, and the FW_190_PLEXGLASS_extr in blue. Both are visibly separated between inside and outside materials: While I'm using the ModelViewer here since I have more control, there's been folks reporting it occuring during gameplay.
-
reported earlier MiG-21 Canopy Bug （The glass flashes）
SASHIBA-11 posted a topic in 3D Model and Cockpit
Select "Cloudy and Rainy 2" and MiG-21 and the glass in the cockpit will flash. This bug only occurs when "Cloudy and Rainy 2" is selected.This bug is also linked to SORC - main warning light button/light Video ↓ I used Google Translate because I can't speak English -
What do you think about having restrictions in-game to your view, while in VR in the cockpit? Have you had experience with such limitations on your view before in other sit-down games? Do you believe that such limits will increase the immersion? Words and comments appreciated as well. Feedback doesn't have to just be from the poll alone. Preferably, it'd be both.
- 47 replies
-
- 2
-
-
- restrictions
- limits
- (and 4 more)
-
Hi guys, I noticed the yellow tinted canopy option seems to be only rendered on the player controlled aircraft and not on the AI controlled Vipers. - Options - Specials - F16 - Canopy Tint: Tinted - Custom mission attached here. Start at Batumi on the apron. 1 player aircraft, 1 AI. Both are using the default livery. - Load mission and go to F2 view. Observe tint only applied on player aircraft. Regards, Sylvain Canopy_Tint_TEST.miz
-
The canopy latch system is not animated. When lowering the canopy, once it touches the cockpit frame, the curved latches then rotate around the canopy mounting points (This is the extra sound you hear after it's closed). Below are screenshots. There are multiple latches around the canopy. All of them should rotate around the canopy mounts to engage and lock the canopy down.
-
As in the title. Players might as well never close the canopy if it costs no speed to them, and only gives more visibility. Same with the P-51. P-47 and Spitfire do have some additional drag, but it's extremely little, only costing a handful of knots of top speed at SL. The drag from an open canopy should probably be a lot higher for those. canopy drag test.trk -
When opening the canopy, it has little or perhaps no additional drag. So players might as well fly around with their canopy always open if it never slows them down. Test is performed by flying at mil power at SL with canopy closed for a couple minutes. Then pull a loop, open the canopy, and continue flying at power at SL. Test also contains the Spitfire, FW190A, and P-47. canopy drag test.trk
-
Bug-WIPER: The wiper does not actually interact with the rain or droplet effects, there are no animations or shaders for streaks, dry streaking, spray accumulation aso. The forward shield also goes "clear" in a boolean state by trigger conditions (seemingly). That "rain droplets" are a clientside-only option and global (by sheer necessity) rain does not interact with modules is neither relevant for the bug nor fit as an explanation pretense. The same issue persists with the Mi-8 HIp module for years. Bug-WIPER-Switch: The mousmap for the wiper-switch in the cockpit covers the entire switch area, suggesting by Eagle and general DCS logic a toogle through the various settings via RMB or LMB. REALITER the actionmaps are extremely tiny for SPECIFIC swtich positions the position labels LMB-only, both breaking the logic applies in DCS in general, while being unergonmic especially if throttle-ministicks or VR solutions are used to interact with the cockpit. That in theory there is a workaround via binding is irrelevant, as this is for simpits mostly in the absence of an actual API, while a normal user will not bind this tertiary binding on the limited buttons on a a HOTAS setting. Reproduction: 100%, global, not system-dependent, no trackfile needed. Workaround: keyboard binding
- 2 replies
-
- 1
-
-
- canopy
- windshield
- (and 10 more)
.png.21a204103c77a0c43197a9527a1c9657.png)
