Special Aircraft Service

Please login or register.

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

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

0 Members and 19 Guests are viewing this topic.

Shermy

  • member
  • Offline Offline
  • Posts: 15
Re: Ultrapack bug report thread (all versions)
« Reply #660 on: April 14, 2023, 12:17:25 PM »

I've encountered a bug with the gunners on a handful of Italian Bombers, specifically the Savoria-Marchetti SM.81 X Early, the SM.81X, the SM.81T and SM.81bis. These aircraft have dorsal, ball (or lower rear fuselage) or waist gunners.  The waist gunners work properly, they track and engage targets. However the dorsal and ball gunners do not work, they deploy but do not track or fire upon enemy aircraft. It should be noted that none of the gunner positions are modeled for player usage on these aircraft. This bug has been replicated on two different systems. I'm using the most updated patch and hotfix. Is there any more info I could share to help solve this bug?
Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23878
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #661 on: April 15, 2023, 01:09:11 AM »

Confirmed for SM.81 series - if any others are affected, please specify.
The original mod has a weird mess of code for retractable turrets - it just can't work that way.
If I ever feel bored enough to waste a week of work on this, I might implement a fully working retractable turret code, but for the time being the hack which has also been implemented in BAT must do: Turrets won't retract, but in return they track and shoot correctly.

Will be part of the next hotfix.

]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 #662 on: April 16, 2023, 11:43:38 AM »

Found an Issue on Defiant Logs found.

Code: [Select]
[2023-04-17 00:53:11.984 UTC +8] dT:    1 java.lang.NullPointerException
[2023-04-17 00:53:11.984 UTC +8] dT:    0 at com.maddox.il2.objects.air.BP_Defiant.update(BP_Defiant.java:109)
[2023-04-17 00:53:11.984 UTC +8] dT:    0 at com.maddox.il2.fm.FlightModelMain.update(FlightModelMain.java:697)
[2023-04-17 00:53:11.984 UTC +8] dT:    0 at com.maddox.il2.fm.FlightModel.FMupdate(FlightModel.java:535)
[2023-04-17 00:53:11.984 UTC +8] dT:    0 at com.maddox.il2.objects.air.NetAircraft$Mirror.fmUpdate(NetAircraft.java:885)
[2023-04-17 00:53:11.984 UTC +8] dT:    0 at com.maddox.il2.fm.FlightModel.update(FlightModel.java:524)
[2023-04-17 00:53:11.984 UTC +8] dT:    0 at com.maddox.il2.fm.FlightModelMain.tick(FlightModelMain.java:706)
[2023-04-17 00:53:11.984 UTC +8] dT:    0 at com.maddox.il2.engine.Interpolators.tick(Interpolators.java:177)
[2023-04-17 00:53:11.984 UTC +8] dT:    0 at com.maddox.il2.engine.Actor.interpolateTick(Actor.java:275)
[2023-04-17 00:53:11.984 UTC +8] dT:    0 at com.maddox.il2.engine.InterpolateAdapter.msgTimeOut(InterpolateAdapter.java:151)
[2023-04-17 00:53:11.984 UTC +8] dT:    0 at com.maddox.rts.MsgTimeOut.invokeListener(MsgTimeOut.java:73)
[2023-04-17 00:53:11.984 UTC +8] dT:    0 at com.maddox.rts.Message._send(Message.java:1217)
[2023-04-17 00:53:11.985 UTC +8] dT:    0 at com.maddox.rts.Message.sendToObject(Message.java:1191)
[2023-04-17 00:53:11.985 UTC +8] dT:    0 at com.maddox.rts.Message.sendTo(Message.java:1134)
[2023-04-17 00:53:11.985 UTC +8] dT:    0 at com.maddox.rts.Message.trySend(Message.java:1115)
[2023-04-17 00:53:11.985 UTC +8] dT:    0 at com.maddox.rts.Time.loopMessages(Time.java:252)
[2023-04-17 00:53:11.985 UTC +8] dT:    0 at com.maddox.rts.RTSConf.loopMsgs(RTSConf.java:17)
[2023-04-17 00:53:11.985 UTC +8] dT:    0 at com.maddox.il2.game.MainWin3D.loopApp(MainWin3D.java:137)
[2023-04-17 00:53:11.985 UTC +8] dT:    0 at com.maddox.il2.game.Main.exec(Main.java:380)
[2023-04-17 00:53:11.985 UTC +8] dT:    0 at com.maddox.il2.game.GameWin3D.main(GameWin3D.java:235)

I found a Bug on Ta-152 canopy Lever No Logs were Found but Photos Taken.






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 #663 on: April 19, 2023, 06:21:05 AM »

Updated Hotfix 18 Status:

P-35 propeller animation not working anymore
Fixed.

Some Buildings are Missing.
Fixed.
In total 79 buildings with various issues have been identified and fixed, some of them using "stand-in" dead meshes.
This should finally get us rid of the "indestructible statics" issue.

FMB, F-84G.
I just noticed the wrong years for F-84G. FMB: 1955 and 1956.
If I'm not mistaken, the correct years are:
1951 - G-1, G-2
1952 - G-3.
Fixed.

bug with the gunners on a handful of Italian Bombers
Fixed for SM.81.
If other bombers are affected too, please report back.

Found an Issue on Defiant Logs found.
Fixed.

I found a Bug on Ta-152 canopy Lever No Logs were Found but Photos Taken.
Fixed.

IL-4 auto autopilot bug: Fixed.

"Static Spawn" Trigger net replication issue: Fixed.

New Message Trigger Option added: Message Triggers can optionally apply only to the player who "triggered" the trigger now, i.e. all players get individual messages from such a message trigger.
This comes in handy e.g. when you want to warn players not to exceed certain altitudes, stay out of certain areas, give hints about waypoints etc.
An "activated by current player only" trigger can optionally be triggered multiple times (default: Just once). There is, however, no choice like "can be trigger <n> times" with "n>1" - either the trigger can be triggered once, or any time repeatedly.

Last but not least, a bug causing trigger messages to be shown off to the left in case of multi-line messages has been fixed, too; alongside with this, the logic of displaying texts from multiple activated triggered has been changed too, they now show up all at once, each with their own centered position and timeout, and each separated by a blank line.

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

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23878
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #664 on: April 20, 2023, 08:51:11 AM »

Another updated Hotfix 18 Status:
All reported and confirmed issues so far are fixed.
Further 12 "stationary" (ships, tanks, cars, airplanes etc.) objects with mesh issues have been fixed.
"Spawn" triggers now can be used to delayed-spawn aircraft according to the Start time set, i.e. when a plane is set to spawn 3 mins after mission start and it's attached as a "target" to a trigger, it will spawn 3mins after the trigger has fired.

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

Shermy

  • member
  • Offline Offline
  • Posts: 15
Re: Ultrapack bug report thread (all versions)
« Reply #665 on: April 20, 2023, 08:57:11 AM »


bug with the gunners on a handful of Italian Bombers
Fixed for SM.81.
If other bombers are affected too, please report back.

Upon testing with the Boulton Paul Defiant I noticed in the QMB that I could not get the aircraft to move. When in a fleet of planes the player's aircraft's propeller would spin but a following AI would be motionless with no propeller movement. In the QMB I managed to load into the cockpit but each time I loaded into the FMB the game would crash. Since these aircraft were stationary an enemy AI aircraft was able to fly around them which triggered the turrets but unfortunately it seems they suffer from the same issue as the Italian gunners.

Using Hotfix 17, I have no crashlog.





These images were taken using the QMB, as stated earlier any attempt to load the plane into FMB crashes the game.
Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23878
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #666 on: April 20, 2023, 09:24:19 AM »

Yes, the Defiant has an issue in Hotfix 17 which was caused by shifting the loadout declarations to files.sfs archive.
Unfortunately previous UP3 versions already had the same loadouts declared in other sfs archives, hence the "new" loadouts get overwritten by "old" ones.
This will get fixed in Hotfix 18.

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

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23878
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #667 on: April 23, 2023, 04:22:38 AM »

Just a quick update regarding the status and schedule of Hotfix 18.
As mentioned earlier, all bugs reported so far are being addressed.
I would have loved to include Wxtech's latest works on layered forest (https://www.sas1946.com/main/index.php/topic,70649.0.html) but that's pending a release of said mod.
Furthermore, for years now we've kept complaining about the Mossie flight model. Vasya once started some work on it, but that apparently stalled in 2019 and to put it mildly, Mr. "know it all" created one big mess (WEP factor 1.63 anyone? lol!).
Last but not least, the changes made in Trigger Net Replication require some maturity checks prior to release.

Two weeks, be sure 8)

]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 #668 on: April 23, 2023, 10:00:02 AM »

Found a Bug on FW-190F-1 Logs Found

Code: [Select]
[2023-04-23 23:58:45.505 UTC +8] dT:    2 INTERNAL ERROR: Can't find '[ClassInfo]' in file '3DO/Cockpit/FW-190A-4/DA4GP2_night.mat'
[2023-04-23 23:58:45.505 UTC +8] dT:    0 WARNING: object '3DO/Cockpit/FW-190A-4/DA4GP2_night.mat' of class 'TMaterial' not loaded
[2023-04-23 23:58:45.505 UTC +8] dT:    0 INTERNAL ERROR: Material: Can't load 'DA4GP2_night.mat'
[2023-04-23 23:58:45.505 UTC +8] dT:    0 Caught Exception in materialReplace(A4GP2_night, DA4GP2_night):
[2023-04-23 23:58:45.505 UTC +8] dT:    0 java.lang.RuntimeException: INTERNAL ERROR: Material: Can't load 'DA4GP2_night.mat'
[2023-04-23 23:58:45.505 UTC +8] dT:    0
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.il2.engine.HierMesh.MaterialReplace(Native Method)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.il2.engine.HierMesh.materialReplace(HierMesh.java:518)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.il2.objects.air.CockpitFW_190A4.reflectCockpitState(CockpitFW_190A4.java:315)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.il2.objects.air.Cockpit.doReflectCockitState(Cockpit.java:574)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.il2.objects.air.Aircraft.setCockpitState(Aircraft.java:2910)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.il2.fm.AircraftState.doSetCockpitState(AircraftState.java:1536)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.il2.fm.AircraftState.setCockpitState(AircraftState.java:1526)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.il2.fm.AircraftState.setEngineState(AircraftState.java:1033)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.il2.fm.AircraftState.hitEngine(AircraftState.java:1043)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.il2.objects.air.Aircraft.msgEndAction(Aircraft.java:643)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.rts.MsgEndAction.invokeListener(MsgEndAction.java:59)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.rts.Message._send(Message.java:1217)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.rts.Message.sendToObject(Message.java:1158)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.rts.Message.sendTo(Message.java:1134)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.rts.Message.trySend(Message.java:1115)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.rts.Time.loopMessages(Time.java:252)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.rts.RTSConf.loopMsgs(RTSConf.java:17)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.il2.game.MainWin3D.loopApp(MainWin3D.java:137)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.il2.game.Main.exec(Main.java:380)
[2023-04-23 23:58:45.505 UTC +8] dT:    0 at com.maddox.il2.game.GameWin3D.main(GameWin3D.java:235)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 java.lang.NullPointerException
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.il2.objects.air.Cockpit.setNightMats(Cockpit.java:585)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.il2.objects.air.CockpitFW_190A4.retoggleLight(CockpitFW_190A4.java:288)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.il2.objects.air.CockpitFW_190A4.reflectCockpitState(CockpitFW_190A4.java:334)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.il2.objects.air.Cockpit.doReflectCockitState(Cockpit.java:574)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.il2.objects.air.Aircraft.setCockpitState(Aircraft.java:2910)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.il2.fm.AircraftState.doSetCockpitState(AircraftState.java:1536)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.il2.fm.AircraftState.setCockpitState(AircraftState.java:1526)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.il2.fm.AircraftState.setEngineState(AircraftState.java:1033)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.il2.fm.AircraftState.hitEngine(AircraftState.java:1043)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.il2.objects.air.Aircraft.msgEndAction(Aircraft.java:643)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.rts.MsgEndAction.invokeListener(MsgEndAction.java:59)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.rts.Message._send(Message.java:1217)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.rts.Message.sendToObject(Message.java:1158)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.rts.Message.sendTo(Message.java:1134)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.rts.Message.trySend(Message.java:1115)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.rts.Time.loopMessages(Time.java:252)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.rts.RTSConf.loopMsgs(RTSConf.java:17)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.il2.game.MainWin3D.loopApp(MainWin3D.java:137)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.il2.game.Main.exec(Main.java:380)
[2023-04-23 23:58:45.568 UTC +8] dT:    0 at com.maddox.il2.game.GameWin3D.main(GameWin3D.java:235)
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 #669 on: April 24, 2023, 07:37:08 AM »

Thanks, KT, I'll check that later.
Meanwhile, let me tell you that we finally have a breakthrough in terms of the teething "cockpit door" bug.
Looks like this was yet another ugly bug introduced with the Claymore 190s pack.
Claymore's 190s contain a code block that is intended to keep players from accidentally opening the canopy when the plane goes faster than 240kph.
Unfortunately, instead of just disabling this on the controls instance level (the correct Java way), Claymore decided to statically disable the player's canopy hotkey once the plane exceeds 240kph and re-enable it once it falls below that speed threshold.
As a result, if either you get shot out of the sky while flying a 190 faster than 240kph, or the mission rolls while you're flying a 190 faster than that, you will subsequently be unable to use your canopy hotkey unless you happen to spawn in another 190 again.

This will get fixed in Hotfix 18.

]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 #670 on: April 26, 2023, 11:40:46 AM »

On the Fw-190V-29, the flaps are incorrectly positioned.

Logged
Mmmm myes pet froge (She/Her)

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 23878
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #671 on: April 26, 2023, 12:06:18 PM »

Thanks. Will get fixed in Hotfix 18.

]cheers[
Mike
Logged
Don't split your mentality without thinking twice.
Pages: 1 ... 53 54 55 [56] 57 58 59 ... 91   Go Up
 

Page created in 0.038 seconds with 25 queries.