Current SPAD.neXt Release: 0.9.12.123

This forum has closed. Please join our Discord Community.

SPAD.neXt online services are no longer available for SPAD.neXt Versions < 0.9.11.5

SPAD.neXt 0.6 Release (Fixup 1.18)

Locked
User avatar
c0nnex
Site Admin
Posts: 5469
Joined: 10 Mar 2015, 21:52
Location: Munich, Germany
Contact:
Status: Offline

SPAD.neXt 0.6 Release (Fixup 1.18)

Post by c0nnex » 12 Sep 2015, 03:37

Changelog from Fixup 1.14
* Fixed crash opening Profile-Edit-Dialog (Aircraft Assignments) when an aircraft is in the FSX/P3D Path which cannot be parsed. (e.g. Title missing in aircraft.cfg)
* Fixed occasional crashes when closing event-configuration dialog with nothing configured
* Fixed Occasional crash sending a "Simulation Control" when SimConnect is disconnected
* FIP Demo: Fixed possible memory leak.
* Licensing: Some Microsoft Update seems to interfere with the Hardware-ID generation. Added some logging
* Forum-feeds: Fixed crash if browser could not be started.
* Changed Panel-Power-off text due to misunderstandings
* Panel-Power-off can now be disabled (just like any other events)
* When switching to an unassigned aircraft it is now possible to select the profile to switch to
* Fixed possible racing condition when sending a lot of keyboard events
* Added Icon for profile-Documentation to profile list
* Moved Color/Appearance to Application wide settings
* Enabled NOTAM to send messages to specific installations
* Fixed occasional crashes when configuring BIP Plates
* Fixed crash when device removed while SPAD.neXt initializes
* Fixed problem with multiple device of same type attached
* Changed default Panel-Status from FSUIPC to SimConnect
* Added some checks when panel go mad ( sending data although no key pressed )

* Updated PMDG 777 profile. Thanks to midnitecwby. Profile Documentation
0.6.Fixup 1.16
* Fixed event-configuration not showing for configured events
* Fixed occasional crash when assigning aircrafts
* Fixed event-configuration accepting empty values
* Added logging of memory and handle usage
0.6 Fixup 1.17
* Fixed crash when configuring Simulation Control
* Fixed eventconfiguration not showing values
* Fixed Multipanel not allowing to configure device power events correctly
* Fixed occasional crash in aircraft assignments
0.6 Fixup 1.18
* Fixed BIP Colors not reseting when switching profiles
* Fixed occasional crash in configuring events when giving no value
* Fixed possible deadlock when switching panels with FIP-Demo active
* Quickstart Guide updated to V0.3 (Thanks to pmb)
* NOTE: If you have a FIP and have the FIP in SPAD.neXt activated, it is recommended to start SPAD.neXt NOT via exe.xml, since it will share ressources with the simulator. So either start manually or disable the FIP in Settings|Saitek.FIP. This will be addressed when FIP-Support is up and running.
SPAD.neXt will automatically update.
The Installer has been updated to this release.

User avatar
c0nnex
Site Admin
Posts: 5469
Joined: 10 Mar 2015, 21:52
Location: Munich, Germany
Contact:
Status: Offline

Re: SPAD.neXt 0.6 Release (Fixup 1.15)

Post by c0nnex » 13 Sep 2015, 19:16

Added 0.6 Fixup 1.16 Chnagelog

User avatar
c0nnex
Site Admin
Posts: 5469
Joined: 10 Mar 2015, 21:52
Location: Munich, Germany
Contact:
Status: Offline

Re: SPAD.neXt 0.6 Release (Fixup 1.17)

Post by c0nnex » 14 Sep 2015, 16:46

Added 0.6. Fixup 1.17 Changelog

User avatar
c0nnex
Site Admin
Posts: 5469
Joined: 10 Mar 2015, 21:52
Location: Munich, Germany
Contact:
Status: Offline

Re: SPAD.neXt 0.6 Release (Fixup 1.18)

Post by c0nnex » 16 Sep 2015, 21:36

0.6 Fixup 1.18
* Fixed BIP Colors not reseting when switching profiles
* Fixed occasional crash in configuring events when giving no value
* Fixed possible deadlock when switching panels with FIP-Demo active
* Quickstart Guide updated to V0.3 (Thanks to pmb)
* NOTE: If you have a FIP and have the FIP in SPAD.neXt activated, it is recommended to start SPAD.neXt NOT via exe.xml, since it will share ressources with the simulator. So either start manually or disable the FIP in Settings|Saitek.FIP. This will be addressed when FIP-Support is up and running.

Locked