Jump to content

Search the Community

Showing results for tags 'Spad'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General Forums
    • Mutley's Hangar News and Announcements
    • Members General & Announcements
    • Real World Aviation
    • Screenshots and Videos
    • Screenshot Contests
    • Classifieds - Flight Sim / Aviation / PC
  • Flight Simulation
    • General
    • Aircraft
    • Scenery
    • Weather Generation & Textures
    • AI / Traffic
    • Missions
    • Flight Planning
    • Flight Sim Adventures
    • Re-painters Workshop
    • Hardware
  • Airport Charts
    • Free Airport Charts
  • Flight Sims
    • Prepar3D Series
    • Flight Simulator X (FSX) / FSX Steam Edition
    • FS2004 (FS9)
    • Dovetail Games Flight Sim World (FSW)
    • X-Plane Series
    • Other Flight Sims
  • Mutley's Hangar Flying Club
    • ATWC Series
    • MEBAR Series
    • MHFC Captains Lounge
  • Miscellaneous Forums
    • Air Hauler
    • Ocala Flight Sim Club Forums

Calendars

  • Community Calendar

Found 2 results

  1. Spad.Next

    Is anyone else using Spad.next? Having used my VR set for a while, I have come to realise that flying in VR, although amazing, isn't something that you want to do all of the time. Its immersive and fantastic in its perceived reality, and so I have set about building a rig that is good for both VR and the more traditional style of FS fun. Spad.Next is a development of the good old Spad alternative drivers for Saitek panels, but is Spad on steroids. It allows for so much more, so much so that support for the Saitek panels is only a backwater in terms of its capabilities. I have two PCs linked together to run my FS. Number one has the FS on it and is a Chillblast machine with plenty of grunt, the second is still a good PC (it was my previous FSX PC) and covers anything that I can run on a second PC to relieve the main PC of extra work. Up until now I have only had Plan-G on this PC, so much of the capability of this PC was not being used. Then I discovered Spad.Next. This provides support for Saitek stuff but is not limited to the Saitek panels. It can support FIPs, yolks, rudder controls and many more devices. It also can run on a second PC. So here is my rig now: PC1 Software. FSX, FSUIPC, SIM Connect, Fly inside (Oculus Rift software), Steves DX10 fixer*. Hardware. Chillblast PC, VR headset, 36" curved monitor, 19" monitor. rudder Peddles Siatek X52 joystick & throttle. PC2 Software. Spad.Next (registered version), Spad.Next virtual FIP addon (registered version), Several FIP gauges, Plan-G. Wide FS, hardware. 1 x 19" monitor, 3 x 7" monitor. PC1 drives the main screen and the one to the left. PC2 drives the right hand screen and all of the small screens. Spad.next allows for the control of Siatek hardware from a second PC. Furthermore it supports remote FIPs and virtual FIPs. This means that cheap 7" VGA monitors can replace expensive Saitek FIP and panels. or indeed any monitor can. So I run FIP gauges on my 7" monitors, and yes you can set it up so that there are several virtual panels on each virtual FIPs so that you can scroll through them. I also have a virtual radio stack on the larger monitor together with Plan-G. Note that the 7" screens show green gauges, this is because I have military gauges showing. colour gauges are available and work just as well. Total cost of Spad.Next with the virtual FIP software is about £60, so less than a single Saitek device. Each additional virtual FIP gauge is about £5 on average for a pay one but there are plenty of free ones. Spad.next comes with all of the Saitek gauges included. * The latest version of Steve's DX 10 fixer comes with a control panel that allows you to switch the DX 10 fixer off and on. Very useful if you use VR Fly inside as the two are not compatible.
  2. SPAD profiles

    Need a bit of advice on SPAD profiles... Each time I fly a new aircraft SPAD adds it to the aircraft listing for me to assign a profile from the different profile types. Is there any way to assign the same profile (e.g. 'single engine prop' which I have set up) to ALL the various 'paints' of that aircraft? At the moment its getting a bit tedious having to go back into SPAD every time I happen to change livery. Its a bit like the way you assign profiles to all varients of an aircraft in FSUIPC by removing the 'paint version' in the .ini file. Cheers guys
×