Special Aircraft Service

Please login or register.

Login with username, password and session length
Advanced search  
Pages: 1 ... 24 25 26 [27] 28 29 30 ... 93   Go Down

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

0 Members and 34 Guests are viewing this topic.

boilingmetal

  • member
  • Offline Offline
  • Posts: 28
Re: Ultrapack bug report thread (all versions)
« Reply #312 on: February 09, 2022, 12:14:41 AM »

Do I need to install to 3.3 update9 befor 3.4?
Yes.

do I need install 3.4 hotfix8 after 3.4?
Yes.

]cheers[
Mike

Thank you for confirming my question!

After I finished installing the 3.3 bigfoot patch, I started the server with the last version SAS selector DS files.
The startup process was very smooth, and I still encountered two java messages of missing ini when loading the task:

Code: [Select]
[2022-02-09 06:54:45.418] dT:    4 IniFile load failed: null
[2022-02-09 06:54:45.418] dT:    0 java.io.FileNotFoundException
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.rts.SFSInputStream.<init>(SFSInputStream.java:47)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.rts.SFSReader.<init>(SFSReader.java:19)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.rts.IniFile.loadFile(IniFile.java:112)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.rts.IniFileDated.loadFile(IniFileDated.java:42)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.rts.IniFile.<init>(IniFile.java:65)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.rts.IniFileDated.<init>(IniFileDated.java:16)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.il2.fm.AircraftState.loadCheaters(AircraftState.java:335)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.il2.fm.AircraftState.update(AircraftState.java:2126)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.il2.fm.AIFlightModel.update(AIFlightModel.java:52)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.il2.ai.air.Maneuver.update(Maneuver.java:953)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.il2.ai.air.Pilot.update(Pilot.java:135)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.il2.fm.FlightModelMain.tick(FlightModelMain.java:614)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.il2.engine.Interpolators.tick(Interpolators.java:177)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.il2.engine.Actor.interpolateTick(Actor.java:275)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.il2.engine.InterpolateAdapter.msgTimeOut(InterpolateAdapter.java:174)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.rts.MsgTimeOut.invokeListener(MsgTimeOut.java:73)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.rts.Message._send(Message.java:1217)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.rts.Message.sendToObject(Message.java:1191)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.rts.Message.sendTo(Message.java:1134)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.rts.Message.trySend(Message.java:1115)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.rts.Time.loopMessages(Time.java:252)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.rts.RTSConf.loopMsgs(RTSConf.java:101)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.il2.game.DServer.loopApp(DServer.java:219)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.il2.game.Main.exec(Main.java:374)
[2022-02-09 06:54:45.418] dT:    0 at com.maddox.il2.game.DServer.main(DServer.java:309)
[2022-02-09 06:54:45.418] dT:    0 IniFile load failed: null
[2022-02-09 06:54:45.434] dT:    0 java.io.FileNotFoundException
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.rts.SFSInputStream.<init>(SFSInputStream.java:47)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.rts.SFSReader.<init>(SFSReader.java:19)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.rts.IniFile.loadFile(IniFile.java:112)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.rts.IniFileDated.loadFile(IniFileDated.java:42)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.rts.IniFile.<init>(IniFile.java:68)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.rts.IniFileDated.<init>(IniFileDated.java:16)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.il2.fm.AircraftState.loadCheaters(AircraftState.java:335)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.il2.fm.AircraftState.update(AircraftState.java:2126)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.il2.fm.AIFlightModel.update(AIFlightModel.java:52)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.il2.ai.air.Maneuver.update(Maneuver.java:953)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.il2.ai.air.Pilot.update(Pilot.java:135)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.il2.fm.FlightModelMain.tick(FlightModelMain.java:614)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.il2.engine.Interpolators.tick(Interpolators.java:177)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.il2.engine.Actor.interpolateTick(Actor.java:275)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.il2.engine.InterpolateAdapter.msgTimeOut(InterpolateAdapter.java:174)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.rts.MsgTimeOut.invokeListener(MsgTimeOut.java:73)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.rts.Message._send(Message.java:1217)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.rts.Message.sendToObject(Message.java:1191)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.rts.Message.sendTo(Message.java:1134)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.rts.Message.trySend(Message.java:1115)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.rts.Time.loopMessages(Time.java:252)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.rts.RTSConf.loopMsgs(RTSConf.java:101)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.il2.game.DServer.loopApp(DServer.java:219)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.il2.game.Main.exec(Main.java:374)
[2022-02-09 06:54:45.434] dT:    0 at com.maddox.il2.game.DServer.main(DServer.java:309)
[2022-02-09 06:55:45.559] dT: 1996 q400Squadron120 (com.maddox.il2.objects.air.A_20G) Init Skill = veteran
[2022-02-09 06:55:45.559] dT:    0 q400Squadron121 (com.maddox.il2.objects.air.A_20G) Init Skill = veteran
[2022-02-09 06:55:45.559] dT:    0 q400Squadron122 (com.maddox.il2.objects.air.A_20G) Init Skill = veteran

After I installed 3.3 update9, when I started the server again, the situation became even worse.
There were a lot of java error messages during the server startup process.

I have used the latest version of the server patch of SAS selector, and modified modtype to 16 corresponding for UP3.

Part of error message encountered during server startup:

Code: [Select]
[7:26:50 AM] 7>[Feb 9, 2022 7:30:58 AM] ------------ BEGIN log session -------------
[7:30:59 AM] Spawn.get( com.maddox.il2.objects.air.D4Y2 ): com.maddox.il2.objects.air.D4Y2
[7:30:59 AM] java.lang.ClassNotFoundException: com.maddox.il2.objects.air.D4Y2
[7:30:59 AM] at com.maddox.rts.LDR.loadClass(LDR.java:20)
[7:30:59 AM] at java.lang.ClassLoader.loadClass(Unknown Source)
[7:30:59 AM] at java.lang.ClassLoader.loadClassInternal(Unknown Source)
[7:30:59 AM] at java.lang.Class.forName0(Native Method)
[7:30:59 AM] at java.lang.Class.forName(Unknown Source)
[7:30:59 AM] at com.maddox.rts.Spawn.get(Spawn.java:39)
[7:30:59 AM] at com.maddox.rts.Spawn.get(Spawn.java:28)
[7:30:59 AM] at com.maddox.il2.game.Main.preloadAirClasses(Main.java:218)
[7:30:59 AM] at com.maddox.il2.game.DServer.beginApp(DServer.java:68)
[7:30:59 AM] at com.maddox.il2.game.Main.exec(Main.java:428)
[7:30:59 AM] at com.maddox.il2.game.DServer.main(DServer.java:335)
[7:30:59 AM] Spawn.get( com.maddox.il2.objects.air.D4Y2S ): com.maddox.il2.objects.air.D4Y2S
[7:30:59 AM] java.lang.ClassNotFoundException: com.maddox.il2.objects.air.D4Y2S
[7:30:59 AM] at com.maddox.rts.LDR.loadClass(LDR.java:20)
[7:30:59 AM] at java.lang.ClassLoader.loadClass(Unknown Source)
[7:30:59 AM] at java.lang.ClassLoader.loadClassInternal(Unknown Source)
[7:30:59 AM] at java.lang.Class.forName0(Native Method)
[7:30:59 AM] at java.lang.Class.forName(Unknown Source)
[7:30:59 AM] at com.maddox.rts.Spawn.get(Spawn.java:39)
[7:30:59 AM] at com.maddox.rts.Spawn.get(Spawn.java:28)
[7:30:59 AM] at com.maddox.il2.game.Main.preloadAirClasses(Main.java:218)
[7:30:59 AM] at com.maddox.il2.game.DServer.beginApp(DServer.java:68)
[7:30:59 AM] at com.maddox.il2.game.Main.exec(Main.java:428)
[7:30:59 AM] at com.maddox.il2.game.DServer.main(DServer.java:335)
[7:30:59 AM] Spawn.get( com.maddox.il2.objects.air.D4Y3 ): com.maddox.il2.objects.air.D4Y3
[7:30:59 AM] java.lang.ClassNotFoundException: com.maddox.il2.objects.air.D4Y3
[7:30:59 AM] at com.maddox.rts.LDR.loadClass(LDR.java:20)
[7:30:59 AM] at java.lang.ClassLoader.loadClass(Unknown Source)
[7:30:59 AM] at java.lang.ClassLoader.loadClassInternal(Unknown Source)
[7:30:59 AM] at java.lang.Class.forName0(Native Method)
[7:30:59 AM] at java.lang.Class.forName(Unknown Source)
[7:30:59 AM] at com.maddox.rts.Spawn.get(Spawn.java:39)
[7:30:59 AM] at com.maddox.rts.Spawn.get(Spawn.java:28)
[7:30:59 AM] at com.maddox.il2.game.Main.preloadAirClasses(Main.java:218)
[7:30:59 AM] at com.maddox.il2.game.DServer.beginApp(DServer.java:68)
[7:30:59 AM] at com.maddox.il2.game.Main.exec(Main.java:428)
[7:30:59 AM] at com.maddox.il2.game.DServer.main(DServer.java:335)
[7:30:59 AM] Spawn.get( com.maddox.il2.objects.air.D4Y3S ): com.maddox.il2.objects.air.D4Y3S
[7:30:59 AM] java.lang.ClassNotFoundException: com.maddox.il2.objects.air.D4Y3S
[7:30:59 AM] at com.maddox.rts.LDR.loadClass(LDR.java:20)
[7:30:59 AM] at java.lang.ClassLoader.loadClass(Unknown Source)
[7:30:59 AM] at java.lang.ClassLoader.loadClassInternal(Unknown Source)
[7:30:59 AM] at java.lang.Class.forName0(Native Method)
[7:30:59 AM] at java.lang.Class.forName(Unknown Source)
[7:30:59 AM] at com.maddox.rts.Spawn.get(Spawn.java:39)
[7:30:59 AM] at com.maddox.rts.Spawn.get(Spawn.java:28)
[7:30:59 AM] at com.maddox.il2.game.Main.preloadAirClasses(Main.java:218)
[7:30:59 AM] at com.maddox.il2.game.DServer.beginApp(DServer.java:68)
[7:30:59 AM] at com.maddox.il2.game.Main.exec(Main.java:428)
[7:30:59 AM] at com.maddox.il2.game.DServer.main(DServer.java:335)
[7:30:59 AM] Spawn.get( com.maddox.il2.objects.air.E13A1 ): com.maddox.il2.objects.air.E13A1
[7:30:59 AM] java.lang.ClassNotFoundException: com.maddox.il2.objects.air.E13A1
[7:30:59 AM] at com.maddox.rts.LDR.loadClass(LDR.java:20)
[7:30:59 AM] at java.lang.ClassLoader.loadClass(Unknown Source)
[7:30:59 AM] at java.lang.ClassLoader.loadClassInternal(Unknown Source)
[7:30:59 AM] at java.lang.Class.forName0(Native Method)
[7:30:59 AM] at java.lang.Class.forName(Unknown Source)
[7:30:59 AM] at com.maddox.rts.Spawn.get(Spawn.java:39)
[7:30:59 AM] at com.maddox.rts.Spawn.get(Spawn.java:28)
[7:30:59 AM] at com.maddox.il2.game.Main.preloadAirClasses(Main.java:218)
[7:30:59 AM] at com.maddox.il2.game.DServer.beginApp(DServer.java:68)
[7:30:59 AM] at com.maddox.il2.game.Main.exec(Main.java:428)
[7:30:59 AM] at com.maddox.il2.game.DServer.main(DServer.java:335)
[7:30:59 AM] Spawn.get( com.maddox.il2.objects.air.F1M ): com.maddox.il2.objects.air.F1M
[7:30:59 AM] java.lang.ClassNotFoundException: com.maddox.il2.objects.air.F1M
[7:30:59 AM] at com.maddox.rts.LDR.loadClass(LDR.java:20)
[7:30:59 AM] at java.lang.ClassLoader.loadClass(Unknown Source)
[7:30:59 AM] at java.lang.ClassLoader.loadClassInternal(Unknown Source)
[7:30:59 AM] at java.lang.Class.forName0(Native Method)
[7:30:59 AM] at java.lang.Class.forName(Unknown Source)
[7:30:59 AM] at com.maddox.rts.Spawn.get(Spawn.java:39)
[7:30:59 AM] at com.maddox.rts.Spawn.get(Spawn.java:28)
[7:30:59 AM] at com.maddox.il2.game.Main.preloadAirClasses(Main.java:218)
[7:30:59 AM] at com.maddox.il2.game.DServer.beginApp(DServer.java:68)
[7:30:59 AM] at com.maddox.il2.game.Main.exec(Main.java:428)
[7:30:59 AM] at com.maddox.il2.game.DServer.main(DServer.java:335)
[7:30:59 AM] Spawn.get( com.maddox.il2.objects.air.G3M2_11 ): com.maddox.il2.objects.air.G3M2_11
[7:30:59 AM] java.lang.ClassNotFoundException: com.maddox.il2.objects.air.G3M2_11
[7:30:59 AM] at com.maddox.rts.LDR.loadClass(LDR.java:20)
[7:30:59 AM] at java.lang.ClassLoader.loadClass(Unknown Source)
[7:30:59 AM] at java.lang.ClassLoader.loadClassInternal(Unknown Source)
[7:30:59 AM] at java.lang.Class.forName0(Native Method)
...
...


There are still STD folders under the #UP# path in the server folder, which contain some ini and properties files.
I also noticed that the original #UP# file has been moved to #UP#_Backup_UP3.3_Patch_9.(/! SAS Common Utils and /Ultrapack 3.3 and /STD)
Under server folder there also a /SFS_UP and /SFS_UP_Backup_UP3.3_Patch_9

Did I miss anything in the process?

I tried add "Files.SFS=ultrapack33.sfs" to il2server.ini, but it is no help.(I deleted this after the installation of 3.4)

Now is the most interesting part:

When I move the server patch of 3.4 with the original directory structure into the server folder and deleted #UP#, most of the error messages disappeared, which these appeared when the mission loading:
Code: [Select]
[2022-02-09 15:55:43.266 UTC +8] dT:    0 Best matching weapon set '2xDT' will be loaded instead now.
[2022-02-09 15:55:46.494 UTC +8] dT:    0 Searching for missing resources...
[2022-02-09 15:55:46.495 UTC +8] dT:    0 Done!
[2022-02-09 15:55:47.082 UTC +8] dT:    0 Loading RRR objects resources data...
[2022-02-09 15:55:47.085 UTC +8] dT:    0 Done.
[2022-02-09 15:55:47.085 UTC +8] dT:    0 Mission: FBDj/JGACE_UAAS14.mis is Loaded
[2022-02-09 15:55:47.086 UTC +8] dT:    0 45>[2022-02-09 15:55:47.090 UTC +8] dT:    0 mission BEGIN
[2022-02-09 15:55:47.097 UTC +8] dT:    0 EventLog Pending Events Checker is running!
[2022-02-09 15:55:47.100 UTC +8] dT:    0 Mission: FBDj/JGACE_UAAS14.mis is Playing
[2022-02-09 15:55:47.100 UTC +8] dT:    0 46>[2022-02-09 15:55:47.262 UTC +8] dT:    5 IniFile load failed: null
[2022-02-09 15:55:47.263 UTC +8] dT:    0 java.io.FileNotFoundException
[2022-02-09 15:55:47.264 UTC +8] dT:    0 at com.maddox.rts.SFSInputStream.<init>(SFSInputStream.java:47)
[2022-02-09 15:55:47.264 UTC +8] dT:    0 at com.maddox.rts.SFSReader.<init>(SFSReader.java:19)
[2022-02-09 15:55:47.265 UTC +8] dT:    0 at com.maddox.rts.IniFile.loadFile(IniFile.java:112)
[2022-02-09 15:55:47.265 UTC +8] dT:    0 at com.maddox.rts.IniFileDated.loadFile(IniFileDated.java:40)
[2022-02-09 15:55:47.266 UTC +8] dT:    0 at com.maddox.rts.IniFile.<init>(IniFile.java:65)
[2022-02-09 15:55:47.267 UTC +8] dT:    0 at com.maddox.rts.IniFileDated.<init>(IniFileDated.java:16)
[2022-02-09 15:55:47.267 UTC +8] dT:    0 at com.maddox.il2.fm.AircraftState.loadCheaters(AircraftState.java:387)
[2022-02-09 15:55:47.268 UTC +8] dT:    0 at com.maddox.il2.fm.AircraftState.update(AircraftState.java:2307)
[2022-02-09 15:55:47.268 UTC +8] dT:    0 at com.maddox.il2.fm.AIFlightModel.update(AIFlightModel.java:52)
[2022-02-09 15:55:47.269 UTC +8] dT:    0 at com.maddox.il2.ai.air.Maneuver.update(Maneuver.java:948)
[2022-02-09 15:55:47.269 UTC +8] dT:    0 at com.maddox.il2.ai.air.Pilot.update(Pilot.java:139)
[2022-02-09 15:55:47.270 UTC +8] dT:    0 at com.maddox.il2.fm.FlightModelMain.tick(FlightModelMain.java:704)
[2022-02-09 15:55:47.278 UTC +8] dT:    0 at com.maddox.il2.engine.Interpolators.tick(Interpolators.java:177)
[2022-02-09 15:55:47.278 UTC +8] dT:    0 at com.maddox.il2.engine.Actor.interpolateTick(Actor.java:275)
[2022-02-09 15:55:47.279 UTC +8] dT:    0 at com.maddox.il2.engine.InterpolateAdapter.msgTimeOut(InterpolateAdapter.java:151)
[2022-02-09 15:55:47.280 UTC +8] dT:    0 at com.maddox.rts.MsgTimeOut.invokeListener(MsgTimeOut.java:73)
[2022-02-09 15:55:47.280 UTC +8] dT:    0 at com.maddox.rts.Message._send(Message.java:1217)
[2022-02-09 15:55:47.281 UTC +8] dT:    0 at com.maddox.rts.Message.sendToObject(Message.java:1191)
[2022-02-09 15:55:47.281 UTC +8] dT:    0 at com.maddox.rts.Message.sendTo(Message.java:1134)
[2022-02-09 15:55:47.282 UTC +8] dT:    0 at com.maddox.rts.Message.trySend(Message.java:1115)
[2022-02-09 15:55:47.282 UTC +8] dT:    0 at com.maddox.rts.Time.loopMessages(Time.java:252)
[2022-02-09 15:55:47.283 UTC +8] dT:    0 at com.maddox.rts.RTSConf.loopMsgs(RTSConf.java:101)
[2022-02-09 15:55:47.283 UTC +8] dT:    0 at com.maddox.il2.game.DServer.loopApp(DServer.java:236)
[2022-02-09 15:55:47.284 UTC +8] dT:    0 at com.maddox.il2.game.Main.exec(Main.java:374)
[2022-02-09 15:55:47.284 UTC +8] dT:    0 at com.maddox.il2.game.DServer.main(DServer.java:337)
[2022-02-09 15:55:47.285 UTC +8] dT:    0 IniFile load failed: null
[2022-02-09 15:55:47.285 UTC +8] dT:    0 java.io.FileNotFoundException
[2022-02-09 15:55:47.286 UTC +8] dT:    0 at com.maddox.rts.SFSInputStream.<init>(SFSInputStream.java:47)
[2022-02-09 15:55:47.287 UTC +8] dT:    0 at com.maddox.rts.SFSReader.<init>(SFSReader.java:19)
[2022-02-09 15:55:47.287 UTC +8] dT:    0 at com.maddox.rts.IniFile.loadFile(IniFile.java:112)
[2022-02-09 15:55:47.288 UTC +8] dT:    0 at com.maddox.rts.IniFileDated.loadFile(IniFileDated.java:40)
[2022-02-09 15:55:47.288 UTC +8] dT:    0 at com.maddox.rts.IniFile.<init>(IniFile.java:68)
[2022-02-09 15:55:47.289 UTC +8] dT:    0 at com.maddox.rts.IniFileDated.<init>(IniFileDated.java:16)
[2022-02-09 15:55:47.289 UTC +8] dT:    0 at com.maddox.il2.fm.AircraftState.loadCheaters(AircraftState.java:387)
[2022-02-09 15:55:47.290 UTC +8] dT:    0 at com.maddox.il2.fm.AircraftState.update(AircraftState.java:2307)
[2022-02-09 15:55:47.290 UTC +8] dT:    0 at com.maddox.il2.fm.AIFlightModel.update(AIFlightModel.java:52)
[2022-02-09 15:55:47.291 UTC +8] dT:    0 at com.maddox.il2.ai.air.Maneuver.update(Maneuver.java:948)
[2022-02-09 15:55:47.291 UTC +8] dT:    0 at com.maddox.il2.ai.air.Pilot.update(Pilot.java:139)
[2022-02-09 15:55:47.292 UTC +8] dT:    0 at com.maddox.il2.fm.FlightModelMain.tick(FlightModelMain.java:704)
[2022-02-09 15:55:47.292 UTC +8] dT:    0 at com.maddox.il2.engine.Interpolators.tick(Interpolators.java:177)
[2022-02-09 15:55:47.293 UTC +8] dT:    0 at com.maddox.il2.engine.Actor.interpolateTick(Actor.java:275)
[2022-02-09 15:55:47.294 UTC +8] dT:    0 at com.maddox.il2.engine.InterpolateAdapter.msgTimeOut(InterpolateAdapter.java:151)
[2022-02-09 15:55:47.294 UTC +8] dT:    0 at com.maddox.rts.MsgTimeOut.invokeListener(MsgTimeOut.java:73)
[2022-02-09 15:55:47.295 UTC +8] dT:    0 at com.maddox.rts.Message._send(Message.java:1217)
[2022-02-09 15:55:47.295 UTC +8] dT:    0 at com.maddox.rts.Message.sendToObject(Message.java:1191)
[2022-02-09 15:55:47.295 UTC +8] dT:    0 at com.maddox.rts.Message.sendTo(Message.java:1134)
[2022-02-09 15:55:47.295 UTC +8] dT:    0 at com.maddox.rts.Message.trySend(Message.java:1115)
[2022-02-09 15:55:47.296 UTC +8] dT:    0 at com.maddox.rts.Time.loopMessages(Time.java:252)
[2022-02-09 15:55:47.296 UTC +8] dT:    0 at com.maddox.rts.RTSConf.loopMsgs(RTSConf.java:101)
[2022-02-09 15:55:47.297 UTC +8] dT:    0 at com.maddox.il2.game.DServer.loopApp(DServer.java:236)
[2022-02-09 15:55:47.297 UTC +8] dT:    0 at com.maddox.il2.game.Main.exec(Main.java:374)
[2022-02-09 15:55:47.298 UTC +8] dT:    0 at com.maddox.il2.game.DServer.main(DServer.java:337)

[2022-02-09 15:56:01.880 UTC +8] dT:  488 46>

I found that in addition to sfs compression and folder structure modification, 3.3 upodate9 still stored some configuration files in #UP#, and deleting them would eliminate java errors in the server startup stage after installing 3.4.
So far, it seems to be good, but there are still some errors that make me feel that something seems to be missing in the middle.

The last part of the error seems to have nothing to do with 3.3 update9, because it is consistent with the error content that appeared after I installed 3.3.
These java messages still indicate that some ini configuration files can't be found. I don't know what I missed before installing 3.3bigfoot. (From the previous discussion about 3.3 server installation, I don't need to install 3.2 first.)
Logged

bomberkiller

  • Treffen sich zwei Jäger...!
  • Modder
  • member
  • Offline Offline
  • Posts: 4929
  • Bf-109G-6/R6 = Bomber Killer
Re: Ultrapack bug report thread (all versions)
« Reply #313 on: February 09, 2022, 04:29:40 AM »

Hello bm,

I would like to give you the following good advice. Refrain from repairing your #UP3.x installation.

Something went wrong in your installation and important files are missing! Install #UP3.4_Cassie from scratch and don't try to extract any zipped files to install them "manually".

A clean install (done correctly) will save you a lot of time and trouble.

I wish you luck.

Best regards

 ]cheers[

Gerhard
Logged
FAC N° 9 ...cheers mein Schatz

boilingmetal

  • member
  • Offline Offline
  • Posts: 28
Re: Ultrapack bug report thread (all versions)
« Reply #314 on: February 09, 2022, 05:34:42 AM »

Hello bm,

I would like to give you the following good advice. Refrain from repairing your #UP3.x installation.

Something went wrong in your installation and important files are missing! Install #UP3.4_Cassie from scratch and don't try to extract any zipped files to install them "manually".

A clean install (done correctly) will save you a lot of time and trouble.

I wish you luck.

Best regards

 ]cheers[

Gerhard

Thank you for your suggestion.

Indeed, assembling a higher version from the foundation is an effective way to eliminate exceptions.
My installation has been gradually upgraded since version 410. At least I confirm that the copy after upgrading to up3.0RC4 has been running smoothly for one month.

From UP3RC4 to 3.3, and then to 3.3update9, I used the wizard of exe file to install completely. During this period, I only manually added SAS selector to confirm the stability of each step.

However, after the installation of 3.3 was completed, there was a java error. These errors remained after I installed 3.4 hotfix8.

step I build up3RC4 server:
1. Install the 4.08 server version(from mission4day)
2. Upgrade 4.09 4.10 4.101 Server Patch
3. Install UP3 RC Client Installer
4. Install server patches for UP3 RC and RC4

after that

1. Install 3.3 client patch, and add SAS selector to test server (with a few errors)
2. Install 3.3 update9 patch, and SAS selector to test server (lots of errors)
3. Copy and overwrite with 3.4 server patch. (lots of errors)
4. Delete #UP#. (with a few errors same as after 3.3 installed)
5. Install up3.4 hotfix8 (same few error)
Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 24036
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #315 on: February 09, 2022, 05:40:45 AM »

Don't worry, everything's fine.
Your latest log shows two errors, both of them triggered by the same command which is used to load an ini file which we've once implemented to detect cheaters.
This is a remnant from internal FAC Server Debugging, it's safe to simply ignore these error messages.

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

boilingmetal

  • member
  • Offline Offline
  • Posts: 28
Re: Ultrapack bug report thread (all versions)
« Reply #316 on: February 09, 2022, 06:02:35 AM »

Don't worry, everything's fine.
Your latest log shows two errors, both of them triggered by the same command which is used to load an ini file which we've once implemented to detect cheaters.
This is a remnant from internal FAC Server Debugging, it's safe to simply ignore these error messages.

]cheers[
Mike

It's great to know this information! My community can now have a complete and clean UP34 server! ! ! !
The best news this year, I can't wait to share it with my guys! They can't play stably in European servers because of the delay problem for a long time.

]cheers[
Logged

bomberkiller

  • Treffen sich zwei Jäger...!
  • Modder
  • member
  • Offline Offline
  • Posts: 4929
  • Bf-109G-6/R6 = Bomber Killer
Re: Ultrapack bug report thread (all versions)
« Reply #317 on: February 10, 2022, 03:17:04 PM »

You're happy, wunderbar!

I'm glad that you were able to solve the problem (with Mike's help).

With best regards

 ]cheers[

Gerhard

PS: Stay safe!
Logged
FAC N° 9 ...cheers mein Schatz

boilingmetal

  • member
  • Offline Offline
  • Posts: 28
Re: Ultrapack bug report thread (all versions)
« Reply #318 on: February 10, 2022, 06:16:17 PM »

A new problem (maybe not so new):

In online mission of many available aircraft(hundreds of models ), after users connect, they need to wait 2-3 minutes before choosing the aircraft for the first spawn. Befor that, they will get an alarm message:
Quote
"Please wait Confirmation of your home base location"...
"Home Base Location not Allocated"
After first spawn, everything is OK.


This situation is particularly evident in a training mission of our community. On this map, all aircraft models of UP30 can be used in several airports.
This mission won't have this problem on the pc-hosting and 3.0RC4 server. After connecting, users can immediately select the airport, aircraft and spawn. However, after upgrading to 3.4 (I didn't test 3.2 and 3.3), this problem appeared in both pc-hosting and dedicated servers.

From other discussions about this alarm information in the forum, it seems to be related to some carrier spawn mechanisms of UP. However, in my mission, there were anomalies in both the air spawn and ground spawn.

I don't know if this is a BUG or a problem that can be solved by adjusting the mission parameters in FMB.


Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 24036
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #319 on: February 10, 2022, 10:42:42 PM »

after users connect, they need to wait 2-3 minutes before choosing the aircraft for the first spawn. Befor that, they will get an alarm message:
Quote
"Please wait Confirmation of your home base location"...
"Home Base Location not Allocated"
After first spawn, everything is OK.

This situation is particularly evident in a training mission of our community. On this map, all aircraft models of UP30 can be used in several airports.
Not an issue but just how it works.
When you don't restrict the available aircraft, Ultrapack has to address all available resources to each and every available aircraft on each and every available airfield.
UP3 RC4 did have a couple of issues in it's MDS code, on of which was that resources were not being distributed correctly to aircraft and airfield (weapons, fuel, ... - per airfield).
This was solved in UP 3.2, which in turn means that all these resource need to be initialized for an airfield before it becomes available to the player.
Now that we have like a thousand available aircraft in UP3.4 (compared to the 400+ in UP3 RC4, and keep the missing MDS init on that version in mind), this simply takes time.

Best practice is not to have airfields with unrestricted aircraft availability on your online mission at all.
It's not that useful anyway.

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

boilingmetal

  • member
  • Offline Offline
  • Posts: 28
Re: Ultrapack bug report thread (all versions)
« Reply #320 on: February 10, 2022, 11:32:11 PM »

after users connect, they need to wait 2-3 minutes before choosing the aircraft for the first spawn. Befor that, they will get an alarm message:
Quote
"Please wait Confirmation of your home base location"...
"Home Base Location not Allocated"
After first spawn, everything is OK.

This situation is particularly evident in a training mission of our community. On this map, all aircraft models of UP30 can be used in several airports.
Not an issue but just how it works.
When you don't restrict the available aircraft, Ultrapack has to address all available resources to each and every available aircraft on each and every available airfield.
UP3 RC4 did have a couple of issues in it's MDS code, on of which was that resources were not being distributed correctly to aircraft and airfield (weapons, fuel, ... - per airfield).
This was solved in UP 3.2, which in turn means that all these resource need to be initialized for an airfield before it becomes available to the player.
Now that we have like a thousand available aircraft in UP3.4 (compared to the 400+ in UP3 RC4, and keep the missing MDS init on that version in mind), this simply takes time.

Best practice is not to have airfields with unrestricted aircraft availability on your online mission at all.
It's not that useful anyway.

]cheers[
Mike

Thank you for your reply!!
! I am relieved to know that this is a normal initialization process, at least I know that this is not a problem caused by any improper installation or use of FMB.

Our community is a group that helps new players in my area get familiar with and enjoy il-2 1946. We may inevitably provide such an amusement park environment for new players in the training map. They need a place to satisfy their curiosity and release their energy before entering more complicated historical battles and tactical missions.

We will try to tell players to wait patiently for a few minutes in the server announcement message.

]cheers[

ps:By the way, are there any better server management tools besides FBDJ, which can be used to realize points management similar to season games and campaigns? In particular, can be used to verify the password of users who log in to the server?In recent years, we have been implementing similar community services through manual management, which really consumes the energy of maintainers.

Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 24036
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #321 on: February 11, 2022, 06:32:15 AM »

There has once been something called "IL-2 Server Manager" (or the like) but it's outdated and has never been my cup of tea.
Honestly FBDj is not that bad once you got used to it.

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

boilingmetal

  • member
  • Offline Offline
  • Posts: 28
Re: Ultrapack bug report thread (all versions)
« Reply #322 on: February 13, 2022, 12:00:59 AM »

There has once been something called "IL-2 Server Manager" (or the like) but it's outdated and has never been my cup of tea.
Honestly FBDj is not that bad once you got used to it.

]cheers[
Mike

Thank you for your answer!

Indeed, compared with other softwares, FBDj is perhaps the most fully functional shareware.
After that, I might try to add some functions based FBDj. Although java16 is relatively old, it is still easier to understand than java13. . .

]cheers[
Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 24036
  • Taking a timeout
    • STFU
Re: Ultrapack bug report thread (all versions)
« Reply #323 on: February 13, 2022, 12:51:51 AM »

Java 1.6 / Java 1.3 you mean.
Java 16 and Java 13 both exist as well and are a completely different cup of tea.
We've carried FBDj a tad further, especially in terms of UP3 compatibility - you might want to get in touch with Skylla about latest sources.

]cheers[
Mike
Logged
Don't split your mentality without thinking twice.
Pages: 1 ... 24 25 26 [27] 28 29 30 ... 93   Go Up
 

Page created in 0.064 seconds with 26 queries.