keith55

What's the best way to set it up? Presumably, the project has to be called Moose_Framework, so it can't co-exist in the same Eclipse workspace as the Master branch. Can I just set up a new workspace, or it better to install a git client and do it the proper way?

I've been playing around with some of the demo missions and I have a couple of questions. What is the recommended way to determine when a plane has reached waypoint? There are some ground unit examples, but I haven't seen anything for aircraft. It would be handy to be able to subscribe to an event, but as far as I can see there isn't one raised. For the SetFileName method on a Radio object, where is it expecting the sound file to be? I've tried giving it an absolute path and various other permutations, but I'm not having much luck. Thanks!

Hopefully, it will be a fairly quick fix.

That's great. Thanks for your help.

Thanks, I missed that. Do I need to download the sound and voice files, too? Where do they need to go?

Well, thanks for checking it out. I've been reading some other threads and it looks as though it's been around for months, if not years. It's a bit disappointing that it hasn't been fixed yet. It's a pretty major bug, and I wouldn't have thought it would be that hard to fix.

OK. great. I have some pedals on order, but I might still occasionally play on a laptop away from home.

The environment seems to be okay now. I've been working through the tutorials and it's working as expected. Setting the folder to be a source folder seems to have fixed the problem. I did uninstall and reinstall it a few times. There were a couple of internal errors reported, but judging by the comments on the video, that seems to be normal. I also had to download moose.lua from an earlier version at github because the pre-release doesn't have it.

Hi, they are both off. They don't make any difference to the problem.

As I described in this thread. Using the keyboard to move the rudder causes it to first move in the desired direction, and the move in the opposite direction and stay there. It makes the game completely unusable. I tried it on two different computers and keyboards and another user in that thread confirmed it. There is a track file attached to the other post.

Thanks, I'll do that.

I thought it was going to be related to the reference to Moose_Framework, but that was set up correctly. The only way to get it to work was right-click=>Build Path=>Use as a source folder

So, the fix was to right-click the folder and choose Build Path=>Use as a source folder

Thanks for checking it. I wonder how I can bring it to the attention of the developers. It makes the Spitfire module unusable for anyone having to use the keyboard.

I'm following the . When I attempt to create a new lua file, I get the following error. I guess it's a simple set-up error somewhere, but I'm not sure where. org.eclipse.dltk.core.ModelException: <project root> [in My_Missions] is not on its project's build path ...Editing this post to add that I can create the a lua file under the automatically generated src directory, but I can't create one under a folder I manually add per the video. I notice that the manual folder and the src directory have different icons. I've searched Eclipse help, but I didn't find a key for the icon used for the src directory.

Hi, Good thought but that's unchecked and take-off assist is zero.

I'm using only the keyboard. I have a problem whereby if I press either the Z or X key, the rudder moves all the way to either the left or right as expected but then it moves all the way to the other side and stays there. So if I press Z,the rudder moves all the way to the left, and then all the way to the right. I've tried this on two different computers with two different keyboards and they both have exactly the same problem. If anyone else could check it that would be much appreciated. To reproduce it. 1. Instant Action=>Spitfire=>Take Off 2. F2 to look at the rear of the plane while it is on the runway. 3 Press X and hold it for a second. In my systems, this causes the rudder to go full left, then full right. I've attached a track file showing the problem. Thanks! SpitfireRudderProblem.trk

I'm all for reality, and if that's the way it works, that's great. I saw a video where a guy playing DCS wearing a headset was making really exaggerated movements, even more so than we would use in real-life. That's what prompted my question. I can't find the video, but if I come across it again, I'll post it.

Did you ever resolve this? I'm having exactly the same problem on the Spitfire.

I'm new to the game and am thinking of pickup up a VR headset. I have a couple of questions. Sorry if they've already been asked. It's a very long thread! I would like to play on one of the warbird servers. From what I've seen, it's mandatory to be looking in all directions, especially behind, all of the time. Videos I've seen of people wearing VR headsets show them making exaggerated movements. For example, if you want to look behind you at 6 o'clock, instead of turning your head to around 4'oclock and moving your eyes to cover to the last part, as we do in real life, it seems that in VR you have to turn your whole body so that you can point your head at 6 o'clock. Does that make it difficult and fatiguing when you are constantly looking behind you in the game? My second question concerned a video I saw on youtube. The guy was pretty negative about the Reverb. His conclusion is "It's not a good option for you, even if you are just using it for simulators.". I wondered if the video had been discussed here. This is the video.

Thanks for that. It was a good idea. I set up a little sight-seeing mission. It's given me practice with the Mission Builder and with navigating, neither of which are too dependent on a joystick.

I think it might be keyboard-dependent. Even the slightest tap on my keyboard was moving the manifold pressure through about a third of its range. I set up a VoiceAttack profile to press the key for 0.01 seconds and that's giving me much smaller increments. It is now usable, but it's still very frustrating. I think I'll wait for the joystick, although I'm sure I won't be able to resist an occasional flight here and there before it arrives.

Thanks for that. Copying the mission helped a lot. I'd only ever flown training missions, so I didn't realise that the norm is to return back to the debrief screen. One problem I encountered was that playing back the mission doesn't show the fly-through hoops in the landing training mission. I did eventually find a way around that, although it is quite convoluted. I managed to improve the keyboard controls by remapping the keys to a very short depression using Voice Attack, but using the keyboard is hard work. As you say, I'll probably be better off waiting for the joystick and reading manuals or something in the meantime.

Hi All, I downloaded the game a couple of days ago, and I've been engrossed ever since. I'm working through the training missions in the TF51D. I'd like to be able to replay the training missions and change the views. I've seen a couple of youtube videos that seem to suggest this should be possible, but I don't seem to be able to get it to work. I've opened the track in the mission editor and the external views checkbox is checked. I'm waiting for a joystick to be delivered and it's going to be a week or so, in the meantime, I struggling by using the keyboard. It's extremely difficult to make small adjustments to the manifold pressure, which makes landing a problem. I was wondering if there is any way to adust this. Cheers,