Special Aircraft Service

Please login or register.

Login with username, password and session length
Advanced search  
Pages: 1 ... 54 55 56 [57] 58 59 60 ... 91   Go Down

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

0 Members and 26 Guests are viewing this topic.

Juliux1337LTU

  • member
  • Offline Offline
  • Posts: 54
Re: Ultrapack bug report thread (all versions)
« Reply #672 on: April 28, 2023, 10:11:21 AM »



Fix this!!!!!!
Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23878
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #673 on: April 28, 2023, 11:32:56 PM »

Fix this!!!!!!
Fix will be available in Hotfix 18. Thans for your report!

Gents, I've stripped all the chatter, fullquotes and other unrelated discussions following GUN123pro's post.
Remember this is a bug report threat.
Please keep it focussed.
Thanks.

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

eol

  • member
  • Offline Offline
  • Posts: 10
Re: Ultrapack bug report thread (all versions)
« Reply #674 on: April 30, 2023, 02:24:33 AM »

Fieseler Fi-103

view from the cockpit - the cockpit frame is applied incorrectly
Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23878
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #675 on: April 30, 2023, 02:31:04 AM »

No clue what you're talking about.
Logged
Don't split your mentality without thinking twice.

eol

  • member
  • Offline Offline
  • Posts: 10
Re: Ultrapack bug report thread (all versions)
« Reply #676 on: April 30, 2023, 08:58:10 AM »

No clue what you're talking about.

Sorry, i can’t attach a image, but it’s enough to look from inside the cockpit

Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23878
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #677 on: April 30, 2023, 09:50:32 AM »

I did.
Still no clue what you're talking about.
Attaching an image should work now - it's just your very first post where you can't post anything containing a link (spam protection).
When you post an image, please don't forget to mark what seems incorrect to you.

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

KingTiger503

  • Legendary History Luftwaffe Elite Ace ,,,
  • Supporter
  • member
  • Offline Offline
  • Posts: 1993
  • KT503 Elite
Re: Ultrapack bug report thread (all versions)
« Reply #678 on: April 30, 2023, 09:37:20 PM »

Some Missing Building were there.

Code: [Select]
[2023-05-01 01:41:25.541 UTC +8] dT:    0 INTERNAL ERROR: Can't open file '3do/Buildings/Pacific/Hangar_Camo/dead.sim'
[2023-05-01 01:41:25.541 UTC +8] dT:    0 WARNING: object '3do/Buildings/Pacific/Hangar_Camo/dead.sim' of class 'SIM' not loaded
[2023-05-01 01:41:25.541 UTC +8] dT:    0 INTERNAL ERROR: MeshObj: Can't load SIM 3do/Buildings/Pacific/Hangar_Camo/dead.sim
[2023-05-01 01:41:25.541 UTC +8] dT:    0 House activateMesh(): Couldn't set mesh "3do/Buildings/Pacific/Hangar_Camo/dead.sim".
[2023-05-01 01:41:25.624 UTC +8] dT:    0 INTERNAL ERROR: Can't open file '3do/Buildings/Pacific/Hangar_Camo/dead.sim'
[2023-05-01 01:41:25.624 UTC +8] dT:    0 WARNING: object '3do/Buildings/Pacific/Hangar_Camo/dead.sim' of class 'SIM' not loaded
[2023-05-01 01:41:25.624 UTC +8] dT:    0 INTERNAL ERROR: MeshObj: Can't load SIM 3do/Buildings/Pacific/Hangar_Camo/dead.sim
[2023-05-01 01:41:25.624 UTC +8] dT:    0 House activateMesh(): Couldn't set mesh "3do/Buildings/Pacific/Hangar_Camo/dead.sim".


Code: [Select]
[2023-05-01 01:41:54.764 UTC +8] dT:    0 ObjState.finalize: Object of com.maddox.il2.objects.vehicles.artillery.RocketryWagon NOT destroyed
[2023-05-01 01:41:54.764 UTC +8] dT:    0 ObjState.finalize: Object of com.maddox.il2.objects.vehicles.artillery.RocketryWagon NOT destroyed
[2023-05-01 01:41:54.764 UTC +8] dT:    0 ObjState.finalize: Object of com.maddox.il2.objects.vehicles.artillery.RocketryWagon NOT destroyed
[2023-05-01 01:41:54.765 UTC +8] dT:    0 ObjState.finalize: Object of com.maddox.il2.objects.vehicles.artillery.RocketryWagon NOT destroyed
[2023-05-01 01:41:54.765 UTC +8] dT:    0 ObjState.finalize: Object of com.maddox.il2.objects.vehicles.artillery.RocketryWagon NOT destroyed
[2023-05-01 01:41:54.765 UTC +8] dT:    0 ObjState.finalize: Object of com.maddox.il2.objects.vehicles.artillery.RocketryWagon NOT destroyed
[2023-05-01 01:41:54.765 UTC +8] dT:    0 ObjState.finalize: Object of com.maddox.il2.objects.vehicles.artillery.RocketryWagon NOT destroyed
[2023-05-01 01:41:54.765 UTC +8] dT:    0 ObjState.finalize: Object of com.maddox.il2.objects.vehicles.artillery.RocketryWagon NOT destroyed
[2023-05-01 01:41:54.765 UTC +8] dT:    0 ObjState.finalize: Object of com.maddox.il2.objects.vehicles.artillery.RocketryWagon NOT destroyed
[2023-05-01 01:41:54.765 UTC +8] dT:    0 ObjState.finalize: Object of com.maddox.il2.objects.vehicles.artillery.RocketryWagon NOT destroyed
[2023-05-01 01:41:54.765 UTC +8] dT:    0 ObjState.finalize: Object of com.maddox.il2.objects.vehicles.artillery.RocketryWagon NOT destroyed
Logged
My Greatest and Best Regards KT503

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23878
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #679 on: May 01, 2023, 12:36:43 AM »

Part 1: Yes, that's known and tackled already. Thanks for the report nevertheless.
Part 2: You forgot to mention that you had connection issues:
Code: [Select]
[2023-04-30 19:41:40.216 UTC +2] dT:   92 socketConnection with 115.135.198.185:62562 on channel 15 lost.  Reason:
[2023-04-30 19:41:40.216 UTC +2] dT:    0 Chat: --- KINGTIGER503 has left the game.
[2023-04-30 19:41:43.140 UTC +2] dT:   97 socket channel '35' start creating: 115.135.198.185:62562
[2023-04-30 19:41:43.375 UTC +2] dT:    8 Chat: --- KINGTIGER503 joins the game.
[2023-04-30 19:41:43.375 UTC +2] dT:    0 socket channel '35', ip 115.135.198.185:62562, KINGTIGER503, is complete created
That's why I always say: Don't snip your logs that short. Give me and us an idea of what happened right before and after the "issue".
This one was simply a connection issue on your end.

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

eol

  • member
  • Offline Offline
  • Posts: 10
Re: Ultrapack bug report thread (all versions)
« Reply #680 on: May 01, 2023, 03:16:01 AM »

I did.
Still no clue what you're talking about.
Attaching an image should work now - it's just your very first post where you can't post anything containing a link (spam protection).
When you post an image, please don't forget to mark what seems incorrect to you.

]cheers[
Mike

I'm sorry, maybe this is not a bug, but that's what I meant

Logged

KingTiger503

  • Legendary History Luftwaffe Elite Ace ,,,
  • Supporter
  • member
  • Offline Offline
  • Posts: 1993
  • KT503 Elite
Re: Ultrapack bug report thread (all versions)
« Reply #681 on: May 01, 2023, 03:40:23 AM »

Fi-103 cockpit had a glitch Bug. From the interior.

Best regards KT503
Logged
My Greatest and Best Regards KT503

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23878
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #682 on: May 01, 2023, 03:50:46 AM »

I'm sorry, maybe this is not a bug, but that's what I meant

Looks to me like you've got a conflicting mod installed, because what I see isn't what you see:


]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 #683 on: May 01, 2023, 04:50:43 AM »

Apparently, the F-72A's canopy moves depending on angle of attack...




Oh, and forgot to mention...

Looks to me like you've got a conflicting mod installed, because what I see isn't what you see:
Apparently this only happens when you Shift + F1
Logged
Mmmm myes pet froge (She/Her)
Pages: 1 ... 54 55 56 [57] 58 59 60 ... 91   Go Up
 

Page created in 0.036 seconds with 24 queries.