Two hours for nothing.

[Missionbug]

Well, continued my Ju-52 career tonight, mission is a two hour long stint in the rain, lovely, no issue there, longest ever done in the game, flew mainly using auto stabilizer so no big deal as far as pilot work load goes.

 

Get home after all that time with no drama and the game confirms I finished and then the screen goes Black and just hangs there, wtf.

 

Eventually I just use task manager to exit the game after starring at the screen for what seems like a eternity and get sent back to the start of the mission.

 

So a tech issue?  Is career bugged?

 

Really annoying, I need to drink some beer now and try and get over how pissed off I am.

 

Sorry, had to share that with you all.

 

Love the game dearly but that [edited] your head.

 

Wishing you all the very best, Pete.

Edited April 16, 2018 by SYN_Haashashin
lenguage

[[APAF]VR_Spartan85]

That’s a pretty crappy ending to a successful flight... perhaps the virtual pilot  passed out after landing..  usually happens to me after a night shift, drive home for an hour then I pass out as soon as the engine is off... wake up in a state of panic cause I don’t know where I am...

 

Let’s hope the next update will fix that from happening again...

 

also, has it happened in any other circumstances?

[Yogiflight]

It is clearly the penalty for cheating by using the auto stabilizer, as the Tante Ju didn't have a 'Kurssteuerung'.

[Fang333333]

I too have experienced the black screen.

[Feathered_IV]

Damn that sucks.  Is is a memory thing suffered especially after long missions?

[Trooper117]

After 2 hours in a mission if that happened to me I'd be more than pissed off.

[Missionbug]

9 hours ago, Yogiflight said:

It is clearly the penalty for cheating by using the auto stabilizer, as the Tante Ju didn't have a 'Kurssteuerung'.

 

I have nerve damage in both arms, auto stab allows me some extra time in game I would not get usually, I can enjoy the scenery that way at least.

 

 

7 hours ago, Feathered_IV said:

Is is a memory thing suffered especially after long missions?

 

It has not happened before but then I never tried two hours in the rain so it just might be that and some kind of pause while the system got its head together after landing, although my system is fairly new and while I do not play ultra it handles the game okay usually.

 

 

Not sure if it is a bug or what, just mentioned it in case it had been seen before, thing is now do I try to fly it again or could it be the mission itself is faulty?

 

 

Anyway, my usual once a week Ju-52 flight was spoiled.

 

 

The old 1946 modded game allows you to create a log, not sure if that is possible for this game but it would certainly be helpful I think to give a indication of what happened.

 

 

Take care guys.

 

Wishing you all the very best, Pete.

 

 

Edited April 15, 2018 by Missionbug

[Yogiflight]

2 hours ago, Missionbug said:

I have nerve damage in both arms, auto stab allows me some extra time in game I would not get usually, I can enjoy the scenery that way at least.

It was just ment as a joke. Even for someone, who doesn't have any issues, it is a very long time to fly actively, what you definitely have to do, when flying a Tante Ju. You have a lot more to do during a flight with her, than with other aircrafts, that fly much smoother.

 

2 hours ago, Missionbug said:

The old 1946 modded game allows you to create a log, not sure if that is possible for this game but it would certainly be helpful I think to give a indication of what happened.

You can do this, by setting 'mission_text_log = 0' to '1'. It is, what is needed when flying PWCG, because Patrick's program uses these files for its AARs. You can find it in the 'startup' file in the 'data' folder of your game. But be aware, by starting it, you will get a lot of Mission Log Files in your 'data' folder, that you have to delete yourself, when not needing them anymore, unless you want to sample them.

 

[Missionbug]

Thank you very much for the information Yogiflight, really appreciated.

 

On checking it looks like the parameter is already set maybe because I have Patrick's utility installed, just need to see if I can make sense of what is there.

 

I might load up the game and see if I can fly the mission again, it seemed to have gone back to the start screen when I restarted last night after the event described so I will pour a beer to help through the flight and see if things turn out the same.

 

 

Wishing you all the very best, Pete.

[Lusekofte]

18 hours ago, Yogiflight said:

It is clearly the penalty for cheating by using the auto stabilizer, as the Tante Ju didn't have a 'Kurssteuerung'.

 

I like to look at it as a comunication-button to my co pilot I just happen to use [A] button when I let him fly

[Yogiflight]

1 hour ago, Missionbug said:

so I will pour a beer to help through the flight and see if things turn out the same.

I think one beer might a bit few for a two hour flight, but you can use the level pilot to get the next ones

 

1 hour ago, 216th_LuseKofte said:

I like to look at it as a comunication-button to my co pilot I just happen to use [A] button when I let him fly

TBH I thought about this as well after I posted this little joke for Missionbug. IRL it surely happens on longer flights, so you are right, why not use this here, too.

[Missionbug]

3 hours ago, 216th_LuseKofte said:

 

I like to look at it as a comunication-button to my co pilot I just happen to use [A] button when I let him fly

 

 

As squadron commander it is my duty to train my pilots in aircraft procedure so I let them fly while I look out the window and enjoy the scenery.

 

There is a video out there that somewhere that actually shows a Ju-52 needing two crew to actually operate it, wtf, and I am supposed to do it myself.

 

 

2 hours ago, Yogiflight said:

I think one beer might a bit few for a two hour flight, but you can use the level pilot to get the next ones

 

TBH I thought about this as well after I posted this little joke for Missionbug. IRL it surely happens on longer flights, so you are right, why not use this here, too.

 

Absolutely right.

 

 

Anyway, I tried the mission again and same result.

 

 

Can any of you that are tech savvy please tell me if this gives any clue to the issue I reported:

 

T:0 AType:15 VER:17
T:0 AType:20 USERID:887d3eda-feac-4124-a020-e933a5d3abf0 USERNICKID:3acaa5cc-5304-426f-9ecc-e8322969435e
T:0 AType:0 GDate:1941.10.19 GTime:15:23:12 MFile:Missions\_gen.msnbin MID: GType:1601 CNTRS:0:0,101:1,201:2 SETTS:111111011110100100000001110 MODS:1 PRESET:1 AQMID:0 ROUNDS: 1 POINTS: 500
T:0 AType:13 AID:736255 COUNTRY:201 ENABLED:1 BC(0,0,0)
T:0 AType:13 AID:738303 COUNTRY:101 ENABLED:1 BC(0,0,0)
T:1 AType:11 GID:795647 IDS:66559,82943,99327 LID:66559
T:1 AType:11 GID:796671 IDS:17407,33791,50175 LID:17407
T:1 AType:11 GID:797695 IDS:592895,609279,625663 LID:592895
T:1 AType:11 GID:798719 IDS:642047,658431 LID:642047
T:1 AType:11 GID:799743 IDS:678911,695295,711679 LID:678911
T:1 AType:11 GID:800767 IDS:150527,127999,159743 LID:150527
T:1 AType:11 GID:801791 IDS:191487,168959,200703 LID:191487
T:1 AType:11 GID:802815 IDS:240639,209919 LID:240639
T:1 AType:11 GID:803839 IDS:288767,258047 LID:288767
T:1 AType:11 GID:804863 IDS:336895,306175 LID:336895
T:1 AType:11 GID:805887 IDS:385023,354303 LID:385023
T:1 AType:11 GID:806911 IDS:424959,402431,434175 LID:424959
T:1 AType:11 GID:807935 IDS:473087,443391 LID:473087
T:1 AType:11 GID:808959 IDS:490495,506879,523263,539647 LID:490495
T:1 AType:14 AID:736255 BP((1016.0,143.4,1160.0),(233807.0,143.4,931.0),(215423.0,143.4,17751.0),(213230.0,143.4,53632.0),(217783.0,143.4,93765.0),(232421.0,143.4,96042.0),(238528.0,143.4,123951.0),(249216.0,143.4,124834.0),(253610.0,143.4,138995.0),(244147.0,143.4,141464.0),(226186.0,143.4,138394.0),(202961.0,143.4,149073.0),(156332.0,143.4,128214.0),(136068.0,143.4,134096.0),(127704.0,143.4,153442.0),(103572.0,143.4,171617.0),(89590.0,143.4,195520.0),(76773.0,143.4,201159.0),(70848.0,143.4,197611.0),(65247.0,143.4,209638.0),(48267.0,143.4,230472.0),(29342.0,143.4,232766.0),(1098.0,143.4,226320.0))
T:1 AType:14 AID:738303 BP((776.0,176.2,231599.0),(29241.0,176.2,237871.0),(51091.0,176.2,234581.0),(66977.0,176.2,214394.0),(72504.0,176.2,202567.0),(76214.0,176.2,205515.0),(92891.0,176.2,198334.0),(106250.0,176.2,175332.0),(132194.0,176.2,156159.0),(140487.0,176.2,136826.0),(155844.0,176.2,132098.0),(203031.0,176.2,152683.0),(225968.0,176.2,142252.0),(245095.0,176.2,144969.0),(258505.0,176.2,140664.0),(251702.0,176.2,120551.0),(242473.0,176.2,120222.0),(235734.0,176.2,93510.0),(221633.0,176.2,89975.0),(217312.0,176.2,52113.0),(219433.0,176.2,20686.0),(242986.0,176.2,1701.0),(279955.0,176.2,1685.0),(279728.0,176.2,242315.0),(732.0,176.2,243248.0))
T:10 AType:9 AID:115711 COUNTRY:101 POS(144570.797, 155.234, 136599.828) IDS(-1,-1,-1)
T:10 AType:9 AID:117759 COUNTRY:101 POS(122596.453, 148.221, 171534.484) IDS(-1,-1,-1)
T:10 AType:9 AID:119807 COUNTRY:101 POS(119634.039, 158.043, 158976.594) IDS(-1,-1,-1,-1,-1,-1,-1,-1)
T:10 AType:9 AID:121855 COUNTRY:101 POS(119634.039, 158.043, 158976.594) IDS(-1,-1,-1,-1,-1,-1,-1,-1)
T:10 AType:9 AID:123903 COUNTRY:101 POS(122596.453, 148.221, 171534.484) IDS(-1,-1,-1)
T:10 AType:9 AID:125951 COUNTRY:101 POS(217546.719, 75.366, 146365.406) IDS()
T:10 AType:9 AID:674815 COUNTRY:201 POS(12701.703, 112.152, 103747.984) IDS(-1,-1,-1,-1,-1)
T:10 AType:9 AID:676863 COUNTRY:201 POS(248642.109, 90.746, 138218.000) IDS(-1)
T:15 AType:12 ID:772095 TYPE:Ju 52 3mg4e COUNTRY:201 NAME:Phillipp von Hase PID:-1 POS(12549.278,114.363,104022.773)
T:15 AType:12 ID:773119 TYPE:BotPilot_Ju52 COUNTRY:201 NAME:BotPilot_Ju52 PID:772095 POS(12550.246,115.205,104024.477)
T:15 AType:10 PLID:772095 PID:773119 BUL:1139 SH:0 BOMB:0 RCT:0 (12549.278,114.363,104022.773) IDS:3acaa5cc-5304-426f-9ecc-e8322969435e LOGIN:887d3eda-feac-4124-a020-e933a5d3abf0 NAME:Missionbug TYPE:Ju 52 3mg4e COUNTRY:201 FORM:0 FIELD:674815 INAIR:1 PARENT:-1 ISPL:1 ISTSTART:1

 

 

 

Or this, not sure if they are the same mission but the only two files that seem to provide any major text entries:

 

T:0 AType:15 VER:17
T:401807 AType:4 PLID:772095 PID:773119 BUL:1139 SH:0 BOMB:0 RCT:0 (13116.352,114.440,104186.117)
T:401808 AType:16 BOTID:773119 POS(13114.475,115.299,104186.648)
T:401809 AType:7
T:401809 AType:12 ID:17407 TYPE:I-16 type 24 COUNTRY:101 NAME:Rostislav Loginov,101495,0 PID:-1 POS(0.000,0.000,0.000)
T:401809 AType:12 ID:18431 TYPE:BotPilot_LaGG3 COUNTRY:101 NAME:BotPilot_LaGG3 PID:17407 POS(0.000,0.000,0.000)
T:401809 AType:4 PLID:17407 PID:18431 BUL:2800 SH:0 BOMB:0 RCT:0 (0.000,0.000,0.000)
T:401809 AType:12 ID:33791 TYPE:I-16 type 24 COUNTRY:101 NAME:Rostislav Danilov,101495,1 PID:-1 POS(0.000,0.000,0.000)
T:401809 AType:12 ID:34815 TYPE:BotPilot_LaGG3 COUNTRY:101 NAME:BotPilot_LaGG3 PID:33791 POS(0.000,0.000,0.000)
T:401809 AType:4 PLID:33791 PID:34815 BUL:2800 SH:0 BOMB:0 RCT:0 (0.000,0.000,0.000)
T:401809 AType:12 ID:50175 TYPE:I-16 type 24 COUNTRY:101 NAME:Demyan Tuseev,101495,1 PID:-1 POS(0.000,0.000,0.000)
T:401809 AType:12 ID:51199 TYPE:BotPilot_LaGG3 COUNTRY:101 NAME:BotPilot_LaGG3 PID:50175 POS(0.000,0.000,0.000)
T:401809 AType:4 PLID:50175 PID:51199 BUL:2800 SH:0 BOMB:0 RCT:0 (0.000,0.000,0.000)
T:401809 AType:12 ID:66559 TYPE:Il-2 mod.1941 COUNTRY:101 NAME:Arsen Shubin,101062,1 PID:-1 POS(0.000,0.000,0.000)
T:401809 AType:12 ID:67583 TYPE:BotPilot_Il2 COUNTRY:101 NAME:BotPilot_Il2 PID:66559 POS(0.000,0.000,0.000)
T:401809 AType:4 PLID:66559 PID:67583 BUL:1800 SH:0 BOMB:0 RCT:0 (0.000,0.000,0.000)
T:401809 AType:12 ID:82943 TYPE:Il-2 mod.1941 COUNTRY:101 NAME:Vsevolod Biryukov,101062,0 PID:-1 POS(0.000,0.000,0.000)
T:401809 AType:12 ID:83967 TYPE:BotPilot_Il2 COUNTRY:101 NAME:BotPilot_Il2 PID:82943 POS(0.000,0.000,0.000)
T:401809 AType:4 PLID:82943 PID:83967 BUL:1800 SH:0 BOMB:0 RCT:0 (0.000,0.000,0.000)
T:401809 AType:12 ID:99327 TYPE:Il-2 mod.1941 COUNTRY:101 NAME:Svyatoslav Bespyatkin,101062,2 PID:-1 POS(0.000,0.000,0.000)
T:401809 AType:12 ID:100351 TYPE:BotPilot_Il2 COUNTRY:101 NAME:BotPilot_Il2 PID:99327 POS(0.000,0.000,0.000)
T:401809 AType:4 PLID:99327 PID:100351 BUL:1800 SH:0 BOMB:0 RCT:0 (0.000,0.000,0.000)
T:401809 AType:12 ID:491519 TYPE:BotPilot_Bf109 COUNTRY:201 NAME:BotPilot_Bf109 PID:490495 POS(171614.781,872.317,127766.648)
T:401809 AType:4 PLID:490495 PID:491519 BUL:1200 SH:0 BOMB:0 RCT:0 (171613.875,872.350,127766.609)
T:401809 AType:12 ID:507903 TYPE:BotPilot_Bf109 COUNTRY:201 NAME:BotPilot_Bf109 PID:506879 POS(173395.703,860.282,127974.664)
T:401809 AType:4 PLID:506879 PID:507903 BUL:1200 SH:0 BOMB:0 RCT:0 (173394.797,860.315,127974.625)
T:401809 AType:12 ID:540671 TYPE:BotPilot_Bf109 COUNTRY:201 NAME:BotPilot_Bf109 PID:539647 POS(173423.047,836.070,127917.922)
T:401809 AType:4 PLID:539647 PID:540671 BUL:1200 SH:0 BOMB:0 RCT:0 (173422.141,836.102,127917.875)
T:401809 AType:12 ID:592895 TYPE:I-16 type 24 COUNTRY:101 NAME:Demyan Stepanov,101495,1 PID:-1 POS(0.000,0.000,0.000)
T:401809 AType:12 ID:593919 TYPE:BotPilot_LaGG3 COUNTRY:101 NAME:BotPilot_LaGG3 PID:592895 POS(0.000,0.000,0.000)
T:401809 AType:4 PLID:592895 PID:593919 BUL:1180 SH:0 BOMB:0 RCT:0 (0.000,0.000,0.000)
T:401809 AType:12 ID:609279 TYPE:I-16 type 24 COUNTRY:101 NAME:Dorofey Ponomaryov,101495,0 PID:-1 POS(0.000,0.000,0.000)
T:401809 AType:12 ID:610303 TYPE:BotPilot_LaGG3 COUNTRY:101 NAME:BotPilot_LaGG3 PID:609279 POS(0.000,0.000,0.000)
T:401809 AType:4 PLID:609279 PID:610303 BUL:1180 SH:0 BOMB:0 RCT:0 (0.000,0.000,0.000)
T:401809 AType:12 ID:625663 TYPE:I-16 type 24 COUNTRY:101 NAME:Rodion Zhuravlyov,101495,3 PID:-1 POS(0.000,0.000,0.000)
T:401809 AType:12 ID:626687 TYPE:BotPilot_LaGG3 COUNTRY:101 NAME:BotPilot_LaGG3 PID:625663 POS(0.000,0.000,0.000)
T:401809 AType:4 PLID:625663 PID:626687 BUL:1180 SH:0 BOMB:0 RCT:0 (0.000,0.000,0.000)
T:401809 AType:12 ID:659455 TYPE:BotPilot_LaGG3 COUNTRY:101 NAME:BotPilot_LaGG3 PID:658431 POS(180466.063,918.242,146534.734)
T:401809 AType:4 PLID:658431 PID:659455 BUL:300 SH:0 BOMB:0 RCT:0 (180465.297,918.334,146535.000)
T:401809 AType:12 ID:679935 TYPE:BotPilot_LaGG3 COUNTRY:101 NAME:BotPilot_LaGG3 PID:678911 POS(144568.625,516.495,137274.422)
T:401809 AType:4 PLID:678911 PID:679935 BUL:1180 SH:0 BOMB:0 RCT:0 (144569.797,516.436,137275.094)
T:401809 AType:12 ID:696319 TYPE:BotPilot_LaGG3 COUNTRY:101 NAME:BotPilot_LaGG3 PID:695295 POS(144276.266,512.948,137202.781)
T:401809 AType:4 PLID:695295 PID:696319 BUL:1180 SH:0 BOMB:0 RCT:0 (144277.563,512.880,137203.188)
T:401809 AType:12 ID:712703 TYPE:BotPilot_LaGG3 COUNTRY:101 NAME:BotPilot_LaGG3 PID:711679 POS(144259.063,509.089,137226.891)
T:401809 AType:4 PLID:711679 PID:712703 BUL:1180 SH:0 BOMB:0 RCT:0 (144260.344,509.019,137227.328)
T:401851 AType:13 AID:736255 COUNTRY:201 ENABLED:1 BC(0,0,3)

 

 

 

Essentially I took the aircraft off myself and then used auto stabilizer for most of the major legs, landed myself at the target airfield Kalinin and took off again after unloading then returned, landed and parked.

 

Same Black screen hang.  Exited with task manager.

 

 

Seems strange that I can fly the entire mission with no issues yet cannot exit that mission at end, I think this is probably a career issue rather than a tech issue with my PC but who knows.

 

 

 

Wishing you all the very best, Pete.

 

 

Edited April 15, 2018 by Missionbug

[RedKestrel]

Have you tried this out in another campaign with another aircraft type? 

[Yogiflight]

52 minutes ago, Missionbug said:

There is a video out there that somewhere that actually shows a Ju-52 needing two crew to actually operate it, wtf, and I am supposed to do it myself.

I saw a video of one of the swiss Ju52s, that are still flying, where you could see, that the second pilot handled the throttle levers during start and landing, and I think on taxiing, too, where you could see how he was braking one side by pulling back the throttle lever, to make a hard turn.

[Missionbug]

47 minutes ago, Yogiflight said:

I saw a video of one of the swiss Ju52s, that are still flying, where you could see, that the second pilot handled the throttle levers during start and landing, and I think on taxiing, too, where you could see how he was braking one side by pulling back the throttle lever, to make a hard turn.

 

 

 It might be that I watched although I thought the one I saw was of a French aircraft, however, same as what I described so that could have been it, looks really difficult to get one of those aircraft onto the ground, passengers do not appreciate what goes on up front.

 

1 hour ago, RedKestrel said:

Have you tried this out in another campaign with another aircraft type? 

 

I only have the one campaign running for the Ju-52, although I just finished Sea Dragons and with that there were no issues but it was scripted.

 

After I posted I went back and started the game again, same as before I could start that particular mission, however, on this occasion I opted to allocate it to another pilot and moved the career forward.

 

So, I elect a mission the day after and fly it on over speed apart from course change and near to the cargo delivery where I take control again.

 

Cargo is off loaded and again I take to the air, follow the way points and eventually make it home where I land, park and exit the mission with no drama and am allowed to proceed.

 

Career then looks okay if I can continue so the mission itself must have been the issue or the inclement weather.

 

Seems strange that all missions prior and the one since were only roughly a hour or so in duration yet the problem one was two.

 

I would think the Ju-52 missions were specific to type of aircraft or role so I guess a He-111 could be used as well because they are not offensive operations because you land and take off again and return to base.

 

So, what was the problem?  A trigger out of place?  Logic screwed for some reason?

 

Maybe we will never know but at least the career itself does not appear to be broken just that one mission so far.

 

Anyway, enough of testing, it is the early morning here now and I need to go to bed.

 

 

 

Wishing you all the very best, Pete.

[RedKestrel]

Perhaps something got corrupted in that particular file that did nit enable the results to be saved?

[Field-Ops]

I actually just got the black screen while playing the "Sirens of Death" Scripted campaign's first mission. I had already played that first mission pre-patch 3.001 and got through to the end no problem. This time I was running VR instead of my regular trackIR because I wanted to test if replays work the same when recorded using VR vs trackIR and to re-experience it with the new Stalingrad map. Anywho I made it all the way to the end of the mission on the runway and just before touchdown my Oculus headset goes dark with the hourglass symbol and I hear my plane touchdown... then crash because I have no clue how to control what i cant see. I took the headset off but the minitor also displayed a black screen so I killed the game with task manager. My saved replay of the 10 mins of being in the missions target area, flying formation, and dropping bombs was corrupted upon re-launch too.

 

At least I learned that flying formation in VR is much easier thanks to that real feeling of depth perception. I couldn't quite get it right when flying with trackIR.