1859

Please note your findings. Do not forget to mention your operating system and the revision of the HELI-X version.
Post Reply
User avatar
Michael
Posts: 1792
Joined: 25 May 2008 16:11
Location: Germany
Contact:

1859

Post by Michael » 27 Dec 2018 20:14

Hello,
you may update to Revision 1859:

1 Revision of nearly all models regarding the ground contact.
2. Minor changes regarding smoke, contact, rope of the lasso training
3. Propeller is kept after crashs
4. Norwegian language updated.

Thank you for your comments.

User avatar
Brian
Posts: 25
Joined: 19 Dec 2018 23:13

Re: 1859

Post by Brian » 28 Dec 2018 18:59

Installed and tested HELI-X (1859) on other hardware platform in conjunction with Debian 9 GNU/Linux OS.

Asus Rock P43R1600 TWINS-WIFI
Pentium Dual-Core CPU E5200, 2.5GHz
Memory 2GB

My transmitter is Futaba T14SG.

Code: Select all

$ uname -a
Linux Napoleon 4.9.0-8-686-pae #1 SMP Debian 4.9.130-2 (2018-10-27) i686 GNU/Linux

$ lspci | grep VGA
08:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1)

$ glxinfo | grep -i vendor
server glx vendor string: NVIDIA Corporation
client glx vendor string: NVIDIA Corporation
OpenGL vendor string: NVIDIA Corporation

$ lspci -v | grep -i audio
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
	Subsystem: ASRock Incorporation 82801JI (ICH10 Family) HD Audio Controller
01:00.0 Multimedia video controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
	Subsystem: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder
01:00.2 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05)
	Subsystem: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port]
08:00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1)
	Subsystem: ASUSTeK Computer Inc. GF119 HDMI Audio Controller

$ java -showversion
openjdk version "1.8.0_181"
OpenJDK Runtime Environment (build 1.8.0_181-8u181-b13-2~deb9u1-b13)
OpenJDK Server VM (build 25.181-b13, mixed mode)

USB-Controller:
[    1.881030] usb 5-1: New USB device found, idVendor=0b9b, idProduct=4012
[    1.881032] usb 5-1: New USB device strings: Mfr=1, Product=4, SerialNumber=0
[    1.881034] usb 5-1: Product: KMODEL Simulator - XTR+G2+FMS Controller
[    1.881035] usb 5-1: Manufacturer: FeiYing Model
[    1.915380] hidraw: raw HID events driver (C) Jiri Kosina
[    1.946464] usbcore: registered new interface driver usbhid
[    1.946465] usbhid: USB HID core driver
[    1.953219] hid-generic 0003:0B9B:4012.0001: hiddev0,hidraw0: USB HID v1.11 Device [FeiYing Model KMODEL Simulator - XTR+G2+FMS Controller] on usb-0000:00:1d.1-1/input0
[    1.956097] input: FeiYing Model KMODEL Simulator - XTR+G2+FMS Controller as /devices/pci0000:00/0000:00:1d.1/usb5/5-1/5-1:1.1/0003:0B9B:4012.0002/input/input1
[    1.956143] hid-generic 0003:0B9B:4012.0002: input,hidraw1: USB HID v1.11 Joystick [FeiYing Model KMODEL Simulator - XTR+G2+FMS Controller] on usb-0000:00:1d.1-1/input1
With GeForce GT 610 in conjunction with the Nvidia driver, the frame rate is between 50 and 60. Scrolling is very smooth.
Once again, it shows, that HELI-X does not need the latest, high performance hardware. Even on an older system, HELI-X runs like a charm.

Issues:
1. When trying to switch to full screen mode HELI-X crashes (reproducible).

Code: Select all

carsten@Napoleon:~/Programme/HELI-X8-Alpha$ ./runHELI-X.sh

handleError
SCHWERWIEGEND o 17:45:58 Uncaught exception thrown in Thread[jME3 Main,6,main]
java.lang.RuntimeException: Unable to find fullscreen display mode matching settings
	at com.jme3.system.lwjgl.LwjglDisplay.createContext(LwjglDisplay.java:79)
	at com.jme3.system.lwjgl.LwjglDisplay.runLoop(LwjglDisplay.java:180)
	at com.jme3.system.lwjgl.LwjglAbstractDisplay.run(LwjglAbstractDisplay.java:232)
	at java.lang.Thread.run(Thread.java:748)
My system supports following resolutions:

Code: Select all

$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
VGA-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 477mm x 268mm
   1920x1080     60.00*+
   1680x1050     59.95  
   1600x1200     60.00  
   1440x900      59.89  
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   640x480       75.00    72.81    59.94  
At least, it would be fine to show a message "Full screen not supported.", instead of crashing the application.
Possibly, the issue is related to https://github.com/jMonkeyEngine/jmonke ... issues/947.

2. Problem Deleting files after airport download
This issue exists on this platform, too. It is reproducible, and independent of the airport being installed.

Code: Select all

carsten@Napoleon:~/Programme/HELI-X8-Alpha$ ./runHELI-X.sh
Exception in thread "Thread-10" java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 46
	at java.util.Vector.get(Vector.java:751)
	at net.HeliX.n.jq.c(Unknown Source)
	at net.HeliX.n.kh.run(Unknown Source)
3. Wheel friction
Some of the planes nearly do not stop after landing. Please check friction settings (tested at Dietersdorf).
For Trojan, I increased WheelFrictionFactorX to 2.5, which seems to be more realistic (can land and taxi within the length of Dietersdorf runway).
For ASW28, I set WheelFrictionFactorX to 3.0.
For RESolution, WheelFrictionFactorX seems to have no effect.
Others (Extra 300) affected, too.

4. Model preview not correct.
As reported by Micha for 1854, the model preview shows the wrong plane (affected: EasyStar, EasyStar_Ailerons, Edge540v3_FC, Opterra, Opterra1_2m, Tortuga)

5. Status line for planes does not show angles for elevator, aileron, and rudder

6. Status line shows wrong rev/min values for some planes
Related to Trojan and Stearman up to 20.000 rev/min is unrealistic.
Related to Opterra, lowest rev/min is apprx. 5000.
(Extra 300 seems to be OK)

7. Tail wheel friction of Extra 300 too low.
When taxiing with very low rev/min. the tail tends to break out extremly.
Wheel friction too low. Taxiing with apprx. 1400 rev/min. result in 25 km/h.

8. Menu View/Zoom shows [null]
What is the meaning of "null" within brackets. "Zoom In [null]", "Zoom Out [null]". I suppose, it should display the assigned keyboard shortcut, which is currently F11 and F12 (Configuration/Controller/Keyboard settings). I tried other keys like i (in) and o (out), but the menu items show [null].

A question:
RESolution has prop now. How can one control the spoiler (airbrakes)?

admin
Administrator
Posts: 4
Joined: 07 Apr 2008 10:35

Re: 1859

Post by admin » 28 Dec 2018 22:03

Thanks for your feedback.
For 8: there are two zoom fucntions for instant zoom and normal zoom. They can be independently configured
RESolution: Choose Idle up 1 or 2. Then aou can control the flaps or the engine, respectively.

admin
Administrator
Posts: 4
Joined: 07 Apr 2008 10:35

Re: 1859

Post by admin » 28 Dec 2018 22:13

And a question regarding 2:
Did you have check a checkbox on the favorite or ignore column? (Airport download window)?

User avatar
Brian
Posts: 25
Joined: 19 Dec 2018 23:13

Re: 1859

Post by Brian » 29 Dec 2018 16:38

For 2: No checkbox, except "HD Update" selected. Whether "HD Update" selected or not makes no difference.

For 8: Configured the "Instant Zoom", and [null] is replaced by the assigned shortcut. After consulting the user manual, I understood the difference between the two zoom functions. Consider to add a note (about the display of [null]) in the user manual.

RESolution: Flight modes work as described. Agility OK for me now. Realistic flight behavior, especially at stall. Thanks.

Post Reply