Special Aircraft Service

Please login or register.

Login with username, password and session length
Advanced search  
Pages: 1 ... 76 77 78 [79] 80 81 82 ... 91   Go Down

Author Topic: Ultrapack bug report thread (all versions)  (Read 98214 times)

0 Members and 11 Guests are viewing this topic.

Juliux1337LTU

  • member
  • Offline Offline
  • Posts: 54
Re: Ultrapack bug report thread (all versions)
« Reply #936 on: October 21, 2023, 08:35:05 AM »

Didnt let fly with RWD-8 and go-229 a-3 night fighter map bugs :-X
Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23878
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #937 on: October 21, 2023, 12:07:56 PM »

Gents, could you do me a favor and check whether the attached file cures the issue with planes not loading?
Just extract the attached zip to your Ultrapack game folder, as a result, in the "#UP#" folder of your game you should have a folder named "UP 3.4 Patch 2 Hotfix 20" containing one file ("B3EDC23283B5A57E").

]cheers[
Mike
Logged
Don't split your mentality without thinking twice.

Froge

  • Pacman Frog
  • member
  • Offline Offline
  • Posts: 361
  • How often should a pfp change?
Re: Ultrapack bug report thread (all versions)
« Reply #938 on: October 21, 2023, 12:51:50 PM »

From what I tested, the cockpits appear now! Thanks Storebror!
(La-5FN)

(BI-1)

(I-16 Type 24)

Logged
Mmmm myes pet froge (She/Her)

Ta183Huckebein

  • FAC #17
  • Modder
  • member
  • Online Online
  • Posts: 1067
  • aka "Raven"
Re: Ultrapack bug report thread (all versions)
« Reply #939 on: October 21, 2023, 03:30:04 PM »

Gents, could you do me a favor and check whether the attached file cures the issue with planes not loading?
Just extract the attached zip to your Ultrapack game folder, as a result, in the "#UP#" folder of your game you should have a folder named "UP 3.4 Patch 2 Hotfix 20" containing one file ("B3EDC23283B5A57E").

]cheers[
Mike

Hey Mike

Since I had nowhere to go today, I went through every single (flyable) plane in UP3 to see if I'd get a nullpointer error. I came up with my list and came here to report it, but then saw you'd posted this.

I went back in and checked my list of planes that I got errors off of, and this has fixed all but four:
He-100D
He-112B-0
He-112B-1
He-112B-2

Log for them:
Code: [Select]
[2023-10-21 16:20:37.206 UTC -5] dT:    0 Mission: Quick/Crimea/CrimeaBlueScramble00.mis is Playing
[2023-10-21 16:20:37.209 UTC -5] dT:    0 +++ com.maddox.il2.objects.air.CockpitHE_112 Fields...
[2023-10-21 16:20:37.216 UTC -5] dT:    0 java.lang.NullPointerException
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.il2.objects.air.CockpitHE_1XX.reflectWorldToInstruments(CockpitHE_1XX.java:667)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.il2.objects.air.Cockpit$Draw.preRender(Cockpit.java:228)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.il2.objects.air.Cockpit.preRender(Cockpit.java:840)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.il2.game.Main3D$RenderCockpit.preRender(Main3D.java:498)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.il2.engine.Renders.doPaint(Renders.java:381)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.il2.engine.Renders.paint(Renders.java:298)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.il2.engine.RendersTicker.msgTimeOut(Renders.java:637)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.rts.MsgTimeOut.invokeListener(MsgTimeOut.java:73)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.rts.Message._send(Message.java:1217)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.rts.Message.sendToObject(Message.java:1191)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.rts.Message.sendTo(Message.java:1134)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.rts.Message.trySend(Message.java:1115)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.rts.Time.loopMessages(Time.java:305)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.rts.RTSConf.loopMsgs(RTSConf.java:18)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.il2.game.MainWin3D.loopApp(MainWin3D.java:137)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.il2.game.Main.exec(Main.java:380)
[2023-10-21 16:20:37.216 UTC -5] dT:    0 at com.maddox.il2.game.GameWin3D.main(GameWin3D.java:235)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 java.lang.NullPointerException
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.il2.objects.air.CockpitHE_1XX.reflectWorldToInstruments(CockpitHE_1XX.java:667)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.il2.objects.air.Cockpit$Draw.preRender(Cockpit.java:228)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.il2.objects.air.Cockpit.preRender(Cockpit.java:840)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.il2.game.Main3D$RenderCockpit.preRender(Main3D.java:498)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.il2.engine.Renders.doPaint(Renders.java:381)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.il2.engine.Renders.paint(Renders.java:298)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.il2.engine.RendersTicker.msgTimeOut(Renders.java:637)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.rts.MsgTimeOut.invokeListener(MsgTimeOut.java:73)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.rts.Message._send(Message.java:1217)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.rts.Message.sendToObject(Message.java:1191)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.rts.Message.sendTo(Message.java:1134)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.rts.Message.trySend(Message.java:1115)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.rts.Time.loopMessages(Time.java:305)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.rts.RTSConf.loopMsgs(RTSConf.java:18)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.il2.game.MainWin3D.loopApp(MainWin3D.java:137)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.il2.game.Main.exec(Main.java:380)
[2023-10-21 16:20:37.217 UTC -5] dT:    0 at com.maddox.il2.game.GameWin3D.main(GameWin3D.java:235)

I also got a curious message series with some of the planes that were fixed, example here from the P-40M:
Code: [Select]
[2023-10-21 16:22:45.915 UTC -5] dT:    0 Mission: Quick/Crimea/CrimeaBlueScramble00.mis is Playing
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ com.maddox.il2.objects.air.CockpitP_40M Fields...
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ java.lang.Float Inner Fields...
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ java.lang.Float Inner Fields...
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ java.lang.Float Inner Fields...
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ java.lang.Float Inner Fields...
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ com.maddox.il2.objects.air.CockpitP_40M$Variables Inner Fields...
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ com.maddox.il2.objects.air.CockpitP_40M needs AnglesFork Init!!! +++
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ com.maddox.il2.objects.air.CockpitP_40M needs AnglesFork Init!!! +++
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ com.maddox.il2.objects.air.CockpitP_40M$Variables Inner Fields...
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ com.maddox.il2.objects.air.CockpitP_40M needs AnglesFork Init!!! +++
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ com.maddox.il2.objects.air.CockpitP_40M needs AnglesFork Init!!! +++
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ com.maddox.JGP.Vector3f Inner Fields...
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ java.lang.Float Inner Fields...
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ java.lang.Float Inner Fields...
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ [F Inner Fields...
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ [F Inner Fields...
[2023-10-21 16:22:45.917 UTC -5] dT:    0 +++ [F Inner Fields...

Also, I got the nullpointer error in the log for the UTI-4, but the plane loaded fine in game, so no idea what that's all about, lol
Logged

KingTiger503

  • Legendary History Luftwaffe Elite Ace ,,,
  • Supporter
  • member
  • Offline Offline
  • Posts: 1993
  • KT503 Elite
Re: Ultrapack bug report thread (all versions)
« Reply #940 on: October 21, 2023, 10:36:33 PM »

The Fw-190 A-4T and D-13T Sea Wulf had a Tail wheel Bug.

 No Logs were found but Photos where taken

Fw-190D13T Sea Wulf




Fw-190A-4T Sea Wulf



Best Regards KT503
Logged
My Greatest and Best Regards KT503

Ta183Huckebein

  • FAC #17
  • Modder
  • member
  • Online Online
  • Posts: 1067
  • aka "Raven"
Re: Ultrapack bug report thread (all versions)
« Reply #941 on: October 21, 2023, 10:38:31 PM »

That's been a thing with those for a long time, KT. I think as long as the mod has been around. Not a UP3 thing (specifically)
Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23878
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #942 on: October 22, 2023, 02:09:50 AM »

The Sea Wulfs have more (and much more important) bugs than just the tailwheel.
Funny to see no one noticed...
They are on the backlog, because: Utterly unimportant, yet lots of work to get them done right. Volunteers welcome!

]cheers[
Mike
Logged
Don't split your mentality without thinking twice.

ssn637

  • member
  • Offline Offline
  • Posts: 171
  • Men mean more than guns in the rating of a ship
Re: Ultrapack bug report thread (all versions)
« Reply #943 on: October 22, 2023, 02:52:47 AM »

I can hardly believe that you solved the issue with nearly all the cockpits by adding a single hex file!  Amazing!
I tried adding it to the 000 Ultrapack 3.4 Cockpits 07.SFS archive provided with Hotfix 20 but couldn't get the affected planes to load, so I left it in the UP#/UP 3.4 Patch 2 Hotfix 20 folder as you'd instructed.
Thanks so much for your dedication and perseverance, Mike!  Bravo zulu!
Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23878
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #944 on: October 22, 2023, 03:08:33 AM »

I went back in and checked my list of planes that I got errors off of, and this has fixed all but four:
He-100D
He-112B-0
He-112B-1
He-112B-2
Thanks for the feedback, very valuable.

Please find an updated Hotfix-fix ( :D ) attached to this post.
Installation is the same, overwrite the previous file if you participated in testing before:

Just extract the attached zip to your Ultrapack game folder, as a result, in the "#UP#" folder of your game you should have a folder named "UP 3.4 Patch 2 Hotfix 20" containing one file ("B3EDC23283B5A57E").

]cheers[
Mike
Logged
Don't split your mentality without thinking twice.

Ta183Huckebein

  • FAC #17
  • Modder
  • member
  • Online Online
  • Posts: 1067
  • aka "Raven"
Re: Ultrapack bug report thread (all versions)
« Reply #945 on: October 22, 2023, 06:10:37 AM »

Thanks for the feedback, very valuable.

Please find an updated Hotfix-fix ( :D ) attached to this post.
Installation is the same, overwrite the previous file if you participated in testing before:

Just extract the attached zip to your Ultrapack game folder, as a result, in the "#UP#" folder of your game you should have a folder named "UP 3.4 Patch 2 Hotfix 20" containing one file ("B3EDC23283B5A57E").

]cheers[
Mike

That appears to have done the trick. All appears to be working so far! (Haven't checked every single previous error plane and the Heinkels, but all Heinkels and a couple other previous seem to be working great!

The Sea Wulfs have more (and much more important) bugs than just the tailwheel.
Funny to see no one noticed...
They are on the backlog, because: Utterly unimportant, yet lots of work to get them done right. Volunteers welcome!

]cheers[
Mike

I'd argue the fact that the wings break off if you fold them on a carrier is a more pertinent issue, honestly. Kinda funny no-one brings that up (almost like nobody ever tests things)
Logged

E69_Haukka

  • member
  • Offline Offline
  • Posts: 62
Re: Ultrapack bug report thread (all versions)
« Reply #946 on: October 22, 2023, 09:52:21 AM »

Thanks for the quick solution! In my case, after installing hotfix 20, I could not access any P-40 aircraft in QMB, and now it is resolved.
A cordial greeting.  ;)
Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23878
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #947 on: October 24, 2023, 08:53:18 AM »

Ultrapack 3.4 Cassie Patch 2 Hotfix 21 has been released: https://www.sas1946.com/main/index.php/topic,67406.msg779765.html#msg779765

]cheers[
Mike
Logged
Don't split your mentality without thinking twice.
Pages: 1 ... 76 77 78 [79] 80 81 82 ... 91   Go Up
 

Page created in 0.03 seconds with 26 queries.