J-man Posted October 21, 2022 Posted October 21, 2022 (edited) --------------------------------------------------------------------------------------------------------- Update: I figured out that I need to own the Super Carrier DLC to use the 2017 Version. My question then is, where is the non-SC Version of this mission?! Are you really trying to force people to buy this stupid DLC by advertising the SU-33 as capable of operating from the russian carrier on the steam page, only to then not offer mission variants that use the base games version of the carrier?? I paid for the SU-33 and the Syria map, and you are telling me you went out of your way to replace the carrier that works for everyone with the DLC version just to get even more money out of me?! Why is there no automatic mechanism that replaces the carrier with the SC version ONLY IF the SC DLC is owned?! Or at least offer a separate version of the mission using the old carrier! Why would I spend 30$ on a DLC that adds US Carriers only to restore functionality to my SU-33 that existed and worked before you CHOSE to kneecap that?! --------------------------------------------------------------------------------------------------------- The player is supposed to spawn on the russian carrier but instead spawns above it in mid-flight. Track can not be attached because apparently the 20 sec. of gameplay are over the 5 MB limit, you can grab it here: https://www.dropbox.com/s/xoeorbktissnyfh/SU-33_Tricolor_SpawnBugged.trk?dl=0 Edited October 21, 2022 by J-man
J-man Posted October 21, 2022 Author Posted October 21, 2022 (edited) Update: The spawn works only if the carrier is exchanged for the old version (pre 2017). Otherwise it appears impossible for the player spawn to happen on the parking position. It is correctly set in the editor, but displayed as on the launch ramp, rather than the parking zone but spawns the player above the ship anyway. If the carrier is using the old model, the player can at least spawn on the start ramp. I just made a new mission featuring the new model of the carrier and I see the same result. Spawning a player-controlled SU-33 on the post 2017 Version of the carrier is not possible. Im playing on the latest OB without any mods btw. Edited October 21, 2022 by J-man
draconus Posted October 24, 2022 Posted October 24, 2022 On 10/21/2022 at 6:51 AM, J-man said: ...only to restore functionality to my SU-33 that existed and worked before you CHOSE to kneecap that?! You're saying this mission worked before with original Kuznietsov? It's just one mission but I agree there should be some warning like: Ramp start works for SC owners. Otherwise you start airborne. Your options: Just start the mission as is and apart from carrier take off it should work fine. Edit the mission and change the carrier. Play other missions - there is whole free Caucasus campaign working with free carrier. Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
J-man Posted October 27, 2022 Author Posted October 27, 2022 On 10/25/2022 at 12:35 AM, draconus said: Edit the mission and change the carrier. Play other missions - there is whole free Caucasus campaign working with free carrier. Thats what I ended up doing. I had already completed the campaigns (ironically there was a bug that spawned me on land and not on the carrier in one mission...) In the end it´s not a big issue to just replace the carrier, but I wish ED would do that themselfs and offer an official non-SC version...
Recommended Posts