Jump to content

Missing tail boom


Dr Zaius

Recommended Posts

If you look out of the window using the look down command (handy for cargo pick up's) then look back torwards the rear of the aircraft you'll note that part of of the boom is missing :noexpression:

 

On closer inspection the gearbox / engine compartment and undercarriage are all missing too!

Screen_200626_224836.thumb.jpg.f8d9dac06e22c0e703156c0d41288e76.jpg

Screen_200626_224843.thumb.jpg.35d42fafb801fccd85403b0e60503f0e.jpg


Edited by Dr Zaius

System Specs: Intel Core i9-9900K 3.6GHz @ 4.8GHz, Gigabyte Z390 Aorus Master, 32 GB G.Skill Trident Z DDR4-3600 RAM, GeForce GTX 4090, Crucial SSD (750 GB), TrackIR 5, TMWH, TM T-Flight Rudder Pedals, Samsung 49” Odyssey G9

Link to comment
Share on other sites

It's not a bug it's a feature! :D

 

I try to explain it, sorry for my english.

 

If you start your mission DCS uses 2 models for your aircraft/module. One is the full glory 3d module you see in the F2...outside view (reduced details in cockpit) and one is your F1 cockpit view, this one has parts of the outside 3d model removed for performance optimisation. With the default F1 cockpit view you would normally never be able to see these things(the view mode you are talking about was added later to the module), so they removed them to increase the performance. If you have VR you will see much more things removed from the model if you leave your cockpit and work outside(F1 view and if you have enough space in your room to do so).

 

This is also true for most/every(?) module in DCS, it's funny in VR if you look what they did remove or didn't care to align, VR wasn't a thing while the development of many of the modules, but performance optimisation was/is.

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

That explaination does make sense thanks but I wonder how much 'performance' is really gained by leaving these static (except for the wheels) graphics out - trackir was well established when this look down view mode was implemented, perhaps then they should have used a locked view :smartass:

System Specs: Intel Core i9-9900K 3.6GHz @ 4.8GHz, Gigabyte Z390 Aorus Master, 32 GB G.Skill Trident Z DDR4-3600 RAM, GeForce GTX 4090, Crucial SSD (750 GB), TrackIR 5, TMWH, TM T-Flight Rudder Pedals, Samsung 49” Odyssey G9

Link to comment
Share on other sites

Mi-8 was developed for DCS 1.x, before there was any sling loading or cargo view cam. You don't see it so why render it - was probably the idea. We still would like to have better performance in DCS, this was just one way to optimise i guess(less geometry and textures to render). Would it hurt performance on todays PC's(DCS Engine is very old - LOMAC)? I don't know but on your screenshots you can only see a fraction of what is "missing". Video is from VR, so sorry for the shaky replay, in VR it's absolutely stable view but not in the track replay.

 


Edited by unknown

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Please, could you explain how to record a VR video with a wide screen image?

 

You play the mission in VR, end the mission and click on "save track" in the result screen. End DCS and start it again without VR mode. Select Replay and record the playback of the track.

This method has 2 disadvantages:

1 you have a shaky cam/view which is not present while gaming in VR

2 the track needs to replay correct, which isn't the case for longer missions every time

 

You could work around problem 1 if you take control over the view while the track is replayed if this is suitable for you.

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

  • Recently Browsing   0 members

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