Redglyph
-
Posts
1644 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Redglyph
-
-
Is it gonna be on Friday.
You said that in your 109th post. It's bad omen ;)
-
For what it's worth, a few other comments / possible improvements.
4) Same, not possible to contact ATC.
5) In the dark again with no instrument lights, apparently no nav lights (though I didn't care to grope in the dark this time). Just make sure to let pass the wingman before or he will undoubtedly run into you, I'm not sure they used to take off in formation in those conditions...
6) In the dark with no instrument lights, possibly no nav lights.
7) Ah, it's not dark again. It should probably be more consistent ;)
I could contact the ATC, this time, so it seems to be only with the Krymsk airfield.
9) Climb & intercept: well, after waiting several minutes for the "Go", I decided to start climbing and I was right ;) Since in the previous mission we had to wait for this signal, maybe it would be less confusing to say "Go", or mention that the pilot can start climbing right away.
Love those contrails, they make quite easy to spot aircraft above flight level :)
-
I don't remember now night flying the 109 but, even turning on panel and cockpit lights? I use to turn them on even in daylight and you can see pretty well everything.
S!
There's the UV light, but I think that's it. Maybe I missed something... a flashlight would be very handy but I don't know whether pilots used them or not (or only their ground crew), I think that mostly they didn't fly at night.
-
I have tried the "campaign" missions, I noticed the following issues.
1) Start-up and taxi
It's night... I'm not sure it's on purpose since mission 2 to take off is during the day. It's also not possible to see the dashboard very well (actually, not at all). It seems some of the circuit breakers and other switches are different from cold & dark settings.
3) Navigation (easy)
I couldn't make the radio communication work with "COMM communication menu", which is normally the only one working in the other missions I've run so far (training & mission 1). I could initiate the menu with "COMM push to talk", however, weird.
The Krymsk ATC does not respond. There is no indication of which channel to use in the briefing or the in-flight instructions, so I first assumed the triangle for ATC, then tried them all but without success.
I opened the mission editor and saw that channel I was set to 39 MHz, which is one of the ATC frequencies, I suppose it corresponds to position I (though in the training and the manual we're told the triangle on position III is for ATC). Still, they don't respond, so the user has to check the map and cheat to find their way to the airfield.
By the way, the manual pp. 61, Figure 49: does not entirely correspond to the Bf 109 radio, the microphone switch is not there and replaced by another switch. Same pp. 106, Figure 93.
-
I should try that, for now I left it on auto. Thanks for testing it, Sporg :)
Yes, I saw the trim in the Special tab, that would be a "ground trim setting" I suppose, I was first hoping it could do the trick and could be controlled by a key but that doesn't seem to be the case. Not that it would be ideal, since cheating and modifying the FM, where I'm merely looking for a way to avoid the joystick spring near neutral where movements are the least precise because of it.
-
Ah, too bad. Thanks for telling me :)
-
I tried by adding this to the comm.lua (for now in the Bf109):
g_crew_items[#g_crew_items + 1] = {name = _('Place wheel chocks'), command = sendMessage.new(Message.wMsgLeaderGroundToggleWheelChocks, true)}
g_crew_items[#g_crew_items + 1] = {name = _('Remove wheel chocks'), command = sendMessage.new(Message.wMsgLeaderGroundToggleWheelChocks, false)}
The menu shows, and the dialog with the ground crew works, but I see no chocks and it doesn't prevent the aircraft from moving. I must be missing something...
I've also tried Message.wMsgGroundCrewWheelChocksOff and Message.wMsgGroundCrewWheelChocksOn, but all those seems to be only dialogs.
-
In combat it wouldn't be necessary. However, it's only a tiny portion of typical missions, where there are long legs for which this would be much appreciated.
-
Anyone? Am I the only one finding this stressing on the wrist?
-
Anyone from the support, please? Could this be fixed?
-
I tried to add the commands to the Joystick/default.lua, but as I was half-expecting, they are ignored:
{down = iCommandPlaneTrimRoll, cockpit_device_id = devices.CONTROL_SYSTEM, value_pressed = -0.1, name = _('Trim Aileron Left'), category = _('Flight Control')}, {down = iCommandPlaneTrimRoll, cockpit_device_id = devices.CONTROL_SYSTEM, value_pressed = 0.1, name = _('Trim Aileron Right'), category = _('Flight Control')},Same for this one,
{action = iCommandPlaneTrimRollAbs, name = _("Trim Aileron")},But it's not really the aircraft trim (which doesn't exist) that I want to control, it's the joystick calibration.
-
If they bring so much to some people, it could just be a kind of "advanced realism" mod for those aircraft.
International business can be tricky sometimes... reminds me of how Valve had to replace blood and shot people by robots leaking oil, among other things ;)
-
The law is the law.:smilewink:
Good reference ;)
-
What usage exactly is forbidden? Waving or wearing it in public is one thing, but having a historic simulation prop, or watching a movie on WWII... is that forbidden as well?
-
It was the same here, and the instructor didn't even have the time to say everything ;)
By comparison, the last training mission uses the active pause to explain the mission and the weapons that will be used, which seems more didactic.
-
Thank you very much for such detailed report.
We'll re-check all the issues you've mentioned here and will fix those that a real bugs. ))
Thanks!
Here's my last one:
5) Ground attack
What the instructor says is cut when passing the first gate. Actually, I think I had the same problem with the landing lesson.
IMHO I think this lesson is too fast-paced, at the beginning the pilot has to adjust the plane for level flight with a lot of transient due to the initial settings, stop the annoying zoom-out that is still forced at the start of any mission, while the instructor keeps talking. Maybe I'm just bad at parallel-tasking (in fact, everyone is), but I find this counter-productive.
I would give a little more time to let the aircraft initialize, and use the correct initial speed of 400 km/h instead of 350 (especially since the aircraft will slow down initially due to the transients).
The climb rate of this aircraft is stunning! What kills me though is the need to compensate the torque with the joystick, I really wish there was a way to trim dynamically to mimick the "static force feedback" (read: the spring...) of a joystick vs the real stick. Made a separate thread on that, I suspect the problem will be the same with the Spitfire.
-
Yes, since I was not sure, I checked the priming part of the start-up and I think I was mislead by an old video illustrating this behaviour, taken when the module was still beta. It must have been fixed since then.
There are still quite a few steps that would be worth including, but I understand there's a balance between a "quick startup guide", which this seems to be closer to, and a real in-depth tutorial, that would require more work. Here it's up to the user to make his/her own in-depth learning.
Hopefully in the future we'll have a more persistent environment, or at least aircraft state, that will encourage to take care of those birds by really using the detailed modelling of the systems, the tear & wear and failures. It seems to me there's a good deal of potential we don't exploit now :)
-
2) Startup (cont'd)
Wow! Didn't catch that the first time. The pilot is told to switch the magnetos before the ground crew is requested to run the inertial starter! Unless there is someone in the crew the pilot hates, I wouldn't recommend that ;)
Maybe it's more cautious to set the governor before starting the engine, especially since it's not tested or reset before.
After pumping, the pilot is told to secure the priming pump down. It's recommended on the P-51 and the Spitfire, but I'm not sure it's possible on this aircraft?
-
Err, that's pretty old, isn't it? Not really a major issue, but landing in those conditions would be very dangerous.
You didn't have any feedback on this, apparently?
-
Hello!
Is there a way to trim the joystick with a shortcut command in DCS, on aircraft that don't have an aileron trim feature? For example the Bf109, and I expect the Spitfire to come.
With some joysticks like the Hotas Warthog, it's quite hard to maintain a slight angle of the joystick because of the spring, and it's not obvious to have precise movements in that situation, past the central zone. On the aircraft there is no spring, so the best way to emulate that would be the possibility to trim the joystick (a little like the Huey).
I have searched a bit but found nothing, maybe I missed this feature?
Note: it's possible to set the center in DCS, but it's a permanent and constant settings, so that's not a solution here, since the trim would depend on the torque and air speed/angle of the aircraft.
-
I confirm it's Senaki for the landing session, and I think I see what the problem is.
- the pilot is told to turn slowly to the right, to face North
- instructions are given by the instructor, with multiple pauses
as those steps take time, even by going quite fast, Sonaki is already well to the East or even SE when the pilot is told to expect an airfield at 1 o'clock.
The aircraft should probably be placed further South-East to avoid this problem.
Landing session (cont'd)
The pilot is told to maintain 300 to 350 km/h indicated air speed, then to lower the gear and the flaps. Flaps should not be extended above 250 km/h, shouldn't this be mentioned? ;) The instructor is quite harrassing about keeping the speed above 300 km/h, so the natural instinct after lowering the landing gear is to maintain that speed.
After the flaps are down, the pilot is told to keep the speed between 250 and 270 km/h...
4) Microphone Static
The recorded instructions have a lot of static, I suppose it's coming from a bad connection to the microphone. At some point, I thought there was a leak somewhere in the plane :D
Well, not a major issue but that sounds a bit ... cheap, maybe it's possible to filter it out and add RF-like static instead to mask it and make it more immersive? Check how it's done in the Maple missions for the A-10C, that was pretty neat :)
-
Mine is 24 May 2016 (though the copyright extends to 2015 only) and it's a fresh install.
Yes, it's annoying there is no version number on those.
-
I'm starting a thread for a few issues I've found in the training missions of the "newly released" Bf-109, maybe it could be also used to gather issues other people see in the training missions.
It's currently version 1.5.4.55952.150.
1) Communication menu
I've noticed that, when coming back with F11, the training log was going up to recover and hide the communication menu, which makes it unreadable. I know a few of the keys so it wasn't a major issue for me, but others may wonder what to do.
You can just wait for a few seconds for the log to disappear, as a work-around. EDIT ... or simply click twice on the push-to-talk or communication menu (always forget which is used for which aircraft), this will scroll the log below :)
As a side note, it would be nice to be able to see the past messages... :)
2) Start-up
I noticed the pressure gauge didn't move when priming. Must confirm that after double-checking in the manual but I was expecting it to raise. It did not prevent the mission from going on very well though.
3) Landing session
I'm told to go North, and then that I should expect a runway to my one o'clock, with red smoke. There is simply no such runway, when this happens the aircraft is already well North of what I think is Senoki (the names are written in white on white on the map, so it's hard to see - already reported but ignored :( ).
I have no idea whether there's an airstrip I should expect, but I went to the point where I'm told to get at 400 m altitude, that happens near a hill that has about that height.
I didn't see any indication in the briefing... it's a bit confusing to be honest. I'll try going South instead of North and see whether it's supposed to be Senoki and update this post as work-around.
-
You have to quit the game, and go back.
Yes, I was wondering the same, since the store is opened from within the module manager, so people tend to remain there, but it seems the module isn't updated (even by refreshing).
Or maybe it was just a coincidence, but that did it for me :)
What will be the first thing you do in the spitfire?
in DCS: Spitfire L.F. Mk. IX
Posted
I will probably look at the manual... then at the aircraft... back at the manual, start a little talk to myself Pulp Fiction-like (ref. Vince back from the dance contest), "You will not fly her directly, you will just look at her, say goodbye, head back home, have a little reading, and only then...". Then I'll probably just get impatient and start her right away :doh: