imacken

No, not at all. I have always been confused by this whole thing about describing the Alpha as a 'space sim' stick. I have owned many different sticks over the years, and I can safely say that, IMO, the Alpha is, by a long way, the best flight stick. I think the space thing must relate to the LEDs on the top, but they are easily disabled in software.

Look at 'completed items' in eBay.

The CM3 adaptor is about £25. Hardly a show stopper!

Ok, so news today from @MAESTR0, he told me that the fix for our issue here will be available in the next update of the map, but that will not be until October! Oh well, I guess it's sort of good news really.

Just ordered mine. Exciting! Introducing the VPC Constellation ALPHA Prime & MongoosT-50CM3 Flightstick Base! - News & Announcements - VIRPIL Controls

Sadly, no change today. There was no update to the Syria map, which I presume is what @Maestro meant by the 'next update'. I'll try messaging him again.

I've just posted all this in the Bugs section here.

I started a thread here which started off with me asking a question about the confusion over CW and non CW bindings in the Spit module. It ended with me taking some time to investigate this behaviour, and coming up with conclusions about what is going on so that we all understand it. Here is what I said in one of the posts in that thread: 'I was interested in what is going on here, so I made some investigations. I deleted (renamed) my Input folder so that DCS would create a new one on demand. I loaded DCS and started in a non-CW mission, made a bind, and a SpitfireLFMkIV folder was created in a new Input folder Quit that mission, loaded a CW one, then the bind above was there from the SpitfireLFMkIV folder I then made a bind while still in CW mission, quit, then loaded a non-CW mission. Bind was there and still only SpitfireLFMkIV folder. However, I then quit out of DCS, reloaded, then started in a CW mission, there were no binds. I made a bind, and then a SpitfireLFMkIVCW folder was created, and the binds applied to the non-CW missions as well. So, conclusion 1) is that whatever variant you start in, the binds in the appropriate folder apply in that session to both variants. This is awkward because, for example, if you start in a non-CW mission, make a bind change, then the next time you load DCS, if you start in a CW mission, the change will not be seen. This means that you have to make any bind changes to both variants by starting a mission for both on a DCS loading, or copy and paste the relevant folder. The next question was, what does selecting from the main DCS UI menu ‘Options>Controls>SpitfireSim’ do? 1) If no mission has been loaded, or, if you loaded a non-CW mission, then changes made there are directed to the SpitfireLFMkIV folder and apply to both variants within that session’s missions. 2) If a CW mission has been loaded and quit from, then any changes in the main DCS menu are applied to the SpitfireLFMkIVCW folder and apply to both variants within that session’s missions. In conclusion, 1) Binds apply to both variants and are dependent on what mission you have loaded first. If it was a non-CW mission, then the binds in SpitfireLFMkIV apply to both within that session. If it was a CW mission, then the binds in SpitfireLFMkIVCW apply to both variants within that session. 2) Changes made in the main UI Options>Controls menu are applied to SpitfireLFMkIV if no mission has been loaded, but if a mission has been loaded then changes are made to the variant folder of the mission that was first loaded. All in all, this seems like a mess, and I’m pretty sure that this is not the way ED want this to work. I feel we should raise (or update) a bug report on this after this. Unless someone else has already come to the same conclusion as me, of course!' So, hopefully, ED will look at this and will now be able to reproduce the issue every time and raise a bug report.

Picked up the Tomcat again after several months away, and I noticed that all my lighting control axes, e.g. AoA Indexer, don't start turning the cockpit dials until 50% rotation on my controllers. Looks OK with full defection in Axis settings. Is this normal behaviour?

I noticed conflicts in the F-14, so I just removed them from my Input Commands file. I was just wondering if there was a non-manual way of checking.

Question, what is the best way to check for duplicate entries as clearly some modules, e.g. F-14, get updated with commands by the devs which causes orange lined duplicates in DCS if they are also in the injector files?

Thanks for that. I'll post a new bug thread here unless you can find the old one.

I was interested in what is going on here, so I made some investigations. I deleted (renamed) my Input folder so that DCS would create a new one on demand. I loaded DCS and started in a non-CW mission, made a bind, and a SpitfireLFMkIV folder was created in a new Input folder Quit that mission, loaded a CW one, then the bind above was there from the SpitfireLFMkIV folder I then made a bind while still in CW mission, quit, then loaded a non-CW mission. Bind was there and still only SpitfireLFMkIV folder. However, I then quit out of DCS, reloaded, then started in a CW mission, there were no binds. I made a bind, and then a SpitfireLFMkIVCW folder was created, and the binds applied to the non-CW missions as well. So, conclusion 1) is that whatever variant you start in, the binds in the appropriate folder apply in that session to both variants. This is awkward because, for example, if you start in a non-CW mission, make a bind change, then the next time you load DCS, if you start in a CW mission, the change will not be seen. This means that you have to make any bind changes to both variants by starting a mission for both on a DCS loading, or copy and paste the relevant folder. The next question was, what does selecting from the main DCS UI menu ‘Options>Controls>SpitfireSim’ do? 1) If no mission has been loaded, or, if you loaded a non-CW mission, then changes made there are directed to the SpitfireLFMkIV folder and apply to both variants within that session’s missions. 2) If a CW mission has been loaded and quit from, then any changes in the main DCS menu are applied to the SpitfireLFMkIVCW folder and apply to both variants within that session’s missions. In conclusion, 1) Binds apply to both variants and are dependent on what mission you have loaded first. If it was a non-CW mission, then the binds in SpitfireLFMkIV apply to both within that session. If it was a CW mission, then the binds in SpitfireLFMkIVCW apply to both variants within that session. 2) Changes made in the main UI Options>Controls menu are applied to SpitfireLFMkIV if no mission has been loaded, but if a mission has been loaded then changes are made to the variant folder of the mission that was first loaded. All in all, this seems like a mess, and I’m pretty sure that this is not the way ED want this to work. I feel we should raise (or update) a bug report on this after this. Unless someone else has already come to the same conclusion as me, of course! Any comments appreciated.

First attachment is what I see when I look down. Second shows that if I move my body down, I can see through the textures and reach the panel! It's the grey panel on the left hand side near the seat that is obscuring the view and I can't get round it, have to go through it! Exactly what is happening with me.

Sorry, but I'm probably not explaining myself well here. Keyboard turn left doesn't work as the side of the seat gets in the way. It's TrackIR I'm talking about, and that is what the screenshots in post #1 are from. It's not about turning left, it's about the side of the seat getting in the way and making the panel inaccessible. The view is too far back. If I look down, then I see the back of the seat textures.

Yep, I've deleted the snapviews.lua just in case. It's impossible for me to access that lighting/stores panel atm as can be seen from the images.

Ah OK, that'll explain it then, thanks. BTW, I tried your method in the other thread, but afaics, you can only vary up/down/left/right. It's forward/back I would like to adjust. However, it's good to know it's not just me!

I appreciate that, thanks. I'm pretty sure I didn't used to have this issue though. I've been away from the Apache for some months now. Why would I be seeing this and no one else does? Something must have changed somewhere for me.

I started another thread on this but it got all mixed up in a off-centre CPG seat debate, which was not the intention, and then @BIGNEWYmerged it, but this is a separate issue for me. Nothing to do with the centre seat issue, so I'm trying again. I’m having trouble with the cockpit view, particularly the CPG, in that I can’t access buttons switches on the back left panel, i.e. lighting/stores/jettison. The seat just gets in the way. It’s like the view is too far back. (See attachments). Any help appreciated on this.

So, I have the same situation in VR. The start position is too far back. I get sections of the back of the seat coming into view. BTW, I 'voted' on the thread.

Yep, another vote for having a seat centred view from me! Feels weird at the moment.

Thanks, yes, something went wrong with the initial post. Hopefully OK now!

I’ve been away from the Apache for a few months, so I apologise if this has been dealt with previously or if I am missing something obvious. I’m having trouble with the cockpit view, particularly the CPG, in that I can’t access buttons switches on the back left panel, i.e. lighting/stores/jettison. The seat just gets in the way. It’s like the view is too far back. (Attachments a1 and a2). Also, the CPG view is not in the centre of the seat. It’s off to the left, which feels very weird. (Attachment a3). Any help appreciated!

Thanks, but not sure how that explains the behaviour we are discussing., i.e. no binds on first CW mission, but CW binds there after loading a non-CW mission.

Just to let you know, it works for the Mustang as well! When in a first mission with blank binds, I loaded the device profiles from P-51D-30-NA folder and all is working perfectly now. Binds are all there, and any change go to all variants. I hope this works for you guys.