-
Posts
1644 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Redglyph
-
-
In this thread from the admittedly small number that don't see the point of it at all. Personal as in, not online discussion, with other simmers.
So yeah, there are people that just want to jump in and go pew pew.
So give them that option, let the admin set it on the server and the rest can have full real or mem-align.
No on has to be unhappy, all markets catered for.
More fifty-fifty if you count them, and it's not "jump in and go pew pew", it's about a lower time and reasons were explained and IMHO are not unreasonable (nothing to do with pew pew crash rince repeat). Some parts are interesting to experience, some others less. If you want to simulate a transatlantic flight, will you really do the whole of it, in real-time? ;)
Realistically the developers have their own priorites anyway, and 8 minutes isn't the same as 30, so it's still bearable - maybe time acceleration will even be a simpler solution to this after all :)
-
Just as an observation, I'm using the English labels in the Ka-50 because it's easier to remember for me, but I found a little unsettling to have the Russian labels in the manual and having to find the English corresponding ones in the cockpit.
It could be the same problem here for people who don't speak French. I'm not sure what is the best way to organize that in the manual, but it's probably worth thinking about. Perhaps the label in the same language as the manual, and between parentheses the original one?
-
-
People are different and while you think it would not add any value, then it doesn't mean everyone thinks that. I made something bold in your post, because that is what a realistic alignment time brings additional value for me: immersion. I play sims like DCS not only to learn how the aircraft works and bring it to use, but also to feel like a pilot as much as possible within the boundaries of the simulation.
Exactly my point, while you think it would add some value, it doesn't mean everyone thinks that. We are both saying the same. Arguably, I may have exaggerated with "a couple of people" to emphasize my point of view - I actually have no idea how much is pro and con.
To me it's not immersive to wait in my chair looking at a screen for 8 minutes, and if it is for you and others, I'm of course respecting that :)
EDIT: reading again your post, I understand the "role playing" part, that's a very good point.
The question remains how to handle that in MP.Good question, indeed. I don't have much MP experience, usually the rules are set on the server aren't they?
How are the other DCS realism settings handled in such case?
when in real life aligment time is 8 min then in dcs aligment time is 8 min. its that easy.if you dont want to wait 8 min play FSX
there is absolutly no reason to shorten this time just because a few people want to play arcade.
Seems you are out of argument ;)
Come on, either bring something constructive to the discussion or just listen, but respect everyone's opinion. As for FSX, Prepar3D, XPlane, IL2, Assetto Corsa, and all the sims I know, there are settings for different levels of realism. There alreay are in DCS too, and as discussed before, it has nothing to do with arcade.
-
Some feet need to be put back on the ground ;) When people say they want realism, it's all about the aircraft sim being as close as possible to the real one, to be immersive, and to allow the users to be precise and focused about what they are doing. Because that's mostly what attracts sim aficionados, they like something a little complicated, they like to do it right, and enjoy the experience.
What is a 8 minutes' wait worth in that regard? It's worth nothing, it does not bring any experience, does not improve your skills, is not enjoyable, so it's utterly useless and it would be silly to compel everyone to be waiting just because a couple of people want to wait so long every single time at take-off. Users don't have to fill in flight plans, flight reports, they don't have to start-up or shutdown their aircraft in all missions, so why would you want to force them doing that?
If you could climb down the ladder, inspect the Mirage and possibly detect some problem (but there aren't any, we know that), and write them down or correct them, that'd be fine. You'd have to remember to start the alignment first, then proceed to the other tasks. If you had other, longer procedures as in the A-10C, that'd be fine, you can start the alignment before starting the engine, and you optimize your start-up time, it's worth it, there's added value. Not here, there's absolutely no added value. Most people have a job, a family, and would rather spend those minutes doing something interesting, I'm sure.
Hence let's just put an option "realistic INS / shortened INS" to keep everyone happy, problem solved. I don't think a single check button on the plane's tab settings would offend anyone, nor take long to implement :) It has been done to translate the cockpit and avionics' language after all - that also was a compromise, I never saw such a debate over it though.
-
Is there a printable listing anywhere for the beacons , ILS and TACAN radio freqs for the NTTR map? I looked in the DOCs folder but did not find anything.
You can check mwd2's link in the similar thread (open alpha 2 forums). They did a pretty good job :)
skyvector.comNo, the frequencies are different, not all NTTR map airports can be found in skyvector or similar websites, the ILS angles are different... as for the Caucasian map, real world != DCS.
-
I wouldn't be surprised if the knob/mouse interaction had some amount of influence from Falcon BMS ;)
-
-
My directions are direct from DCS (nose wheel on centerline and velocity indicator on the last centerline at the end of the runway).
It would be better if the ILS stays, sometimes we have bad weather ;)
I wrote many bug reports for the bugs (RWY direction deviation, ect) but the ED support team.... they are not interested in make the sim better. I wrote bug reports so many times :noexpression:
We need the beacons and frequencies in the F10 map, i wrote it since 1991... ok no, but in 2013. And it tooks this long time until we have the data in the map. And nevertheless in the NTTR map the ILS data is missing :doh: And a scrollable kneeboard map (like in real aviation) is missing, too.
254 is UHF (not exactly, because VHF goes up to 300MHz) and 39 is HF (normally only goes up to 30 MHz)
I agree, that's probably best to keep ILS for those airports which don't have any, it's safer ;) I'm just reporting the real frequencies I found, up to the dev to see what they do with the information.
Thanks for the info, I thought those were something like that, for example for older planes that don't go as high as UHF. I have no idea whether those are real or not though, I don't think so.
Yes, it'd be nice to get the ground charts for NTTR, but this map is still early in its infancy, let's be patient :) I have taken a few ground charts for Nellis, McCarran and that's all the public information I could find, I'll put them in attachment - but the frequencies are not correct so you'll have to modify that if you use it for a temporary kneeboard.
-
That's something that was bothering me too (I think similar differences exist for the Caucasian map).
In red the corrections that are needed, in green what seems correct:
I have 209°/109.1 MHz for KLSV/Nellis 21L (source, source).
No ILS for KINS/Creech (source).
For KLAS/McCarran (source):
- 255°/110.3 MHz/Ch. 40 for 25R
- 255°/111.75 MHz/Ch. 54 for 25L
- 10°/110.1 MHz/Ch. 38 for 01L
- no ILS for the others (19R, 01R, 19L, 07L, 07R)
No info for KXTA/"Groom Lake" ;)
The ATC frequencies seem to be all wrong too (in MHz below):
- Nellis: 132.55, 327.00 (and not 125.00, not sure what 39.20 and 254.00 are)
- Creech: 118.30, 360.625 (and not 122.00)
- McCarran: 118.75 (01L/19R, 01R/19L), 119.90 (07L/25R, 07R/25L), 257.80 (and not 124.00)
- KXTA: no info.
-
1
-
-
No, it doesn't, but what I mean is I already asked whether it was worth going further, and derelor didn't seem to say so. Since he gave this "spec" and already helped with the same issue on the A-10C, he must know how those switches are supposed to behave anyway ;)
If only we could see the tickets, that'd be easier.
-
Do you know whether the report covers the logic between right and left mouse clicks? AFAICT the M-2000C has this consistently reversed as compared to all other modules. E.g. on rotary switches, right clicks should be clockwise, left clicks should be counter-clockwise. The M-2000C Radar Mode Selector, among others, works the other way around.
I'm just asking because I'd be willing to compile a list of all buttons and switches that come to my attention, but if this is already (indirectly) included in the ticket, there'd be little use of doing double work. ;)
Erm, that's what I was asking when starting this thread. But apparently they are aware they have to review all this, hopefully soon because it's really disturbing. But yes, all knob switches are reversed apart from these three I think:
- INS Operational Mode
- EW Mode Selector Switch
- Gun Target Wingspan
(except those which aren't implemented yet, of course). Same with the 3-way switches, except a few like Bomb Fuse Selector Switch for example.
And then there are some ugly cases like the TACAN Mode select implemented as an analogue knob, and the HSI Heading being implemented as a switch.
Agreed. Mostly it's limited to the A-10 and the M-2000C, but a few other modules have the left/right "backwards" relative to what I think of as natural, at least.... or relative to the specs linked in the 1st post. I think those aircraft should have consistent controls.
-
Incomplete ? Is not even there!
(Error 404)!
AC
What are you refering to?
-
Further comment on this aircraft moving. Here it's obviously dependent on the start-up method, (1) and (2). It also depends on the throttle, probably, I've seen many videos where people put the throttle quite far, it seems we lack the IDLE position of this throttle, and a STOP position (although there is a stop button...).
Otherwise, no, those aircraft don't move when the engine is starting, that would be dreadful and terrible design :D
[ame]
[/ame][ame]
[/ame][ame]
[/ame] -
I'm still puzzled by the start-up procedure, concerning (1) the power switches and the status lights, and (2) the starter fuel pump and ignition/vent switches.
(1) separate thread, where I've reported some issues on the start-up procedure.
(2) Start-up pump:
In the "leaked" pilot's flight manual, there is no mention of switching off the starter during the start-up procedure. It is just mentioned that it stops after 35 seconds when N=19% during the dry ventilation procedure.
It's also mentioned in the parking procedure that, after the engine is stopped, "BP and fire extinguisher -> stop".
Should we deduce that it's stopping automatically after 35", even in the normal procedure?
Finally, still in this French manual, there is an interruption procedure (pp. 9):
- throttle on STOP- ignition/vent on VENT (ventilation)
- wait for the automatic stop of the starter, which allows ventilation
In case of emergency:
- throttle on STOP
- switch off the BP (which stops the starter).
This seems to suggest the starter fuel pump is only switched off in case of emergency, do you also interpret it like that?
-
Given the "aircraft moving forward" issue and the unclear power sources during the start-up procedure, I have tried three different methods.
In summary,
(1) follows the RAZBAM manual, without battery
(2) directly switches battery ON
(3) directly switches battery, transfer and alternators ON
-> (1) and (2) yield an audio warning when the engine starts, and the aircraft moves forward
-> (3) follows the leaked (French) Mirage 2000-C pilot's flight manual, and seems better
There are other issues like the status lights and especially the starter pump which misbehaves.
Here are the details below, I think the actual procedure needs clarifying, and the little quirks in warning lights should be addressed.
I had a look at a video of the M2M Mirage, but it seemed very fancy (even though it's supposed to have been validated by guys from the French AF, but I'm not sure it's about this part), so I didn't push the comparison further.
See also the thread on the manual.
Finally, there is the stable values of RPM and Tt7:
> N down and stable at 49%
> Tt7 down and stable at 650 °C
Shouldn't these be 47-48% (close enough), and 480 °C (ref. manual pp. 9, lectures courantes, ralenti au sol)?
========================================================= METHOD 1
- parking handle raised
- vent/ignition on D or G
> audio warning
- audio warning reset
> BATT, HUILE, B.P, BP.G, BP.D, HYD.1, HYD.2, HYD.S, PARK
** error: TRN, ALT1, ALT2 should be ON
- engine fuel pump L and R ON
> BATT, HUILE, HYD.1, HYD.2, HYD.S, PARK (-B.P, BP.G, BP.D)
** error: B.P light should be ON
** actually, B.P switches off when either BP, engine fuel L or R is ON
** error: TRN, ALT1, ALT2 should be ON
- either starter pump ON, or open the engine start cover
- wait for B.P OFF
> BATT, HUILE, HYD.1, HYD.2, HYD.S, PARK
** error: TRN, ALT1, ALT2 should be ON
- click on engine start for 1 second
- wait for N >= 10%
> BATT, HYD.1, HYD.2, HYD.S, PARK (-HUILE)
** error: TRN, ALT1, ALT2 should be ON
- throttle on idle
> BATT, ALT1, ALT2, HYD.1, HYD.S, PARK
** error: TRN should be on, HYD.1 should be off
> audio warning at N=20%
- audio warning reset
> Tt7 climbs to 800 °C
> N climbs to 75% and aircraft moves forward ~50 cm
> N down and stable at 49
> Tt7 down and stable at 650 °C
> BATT, ALT1, ALT2, HYD.1, HYD.S, PARK
- main battery ON
> TRN, ALT1, ALT2, HYD.1, HYD.S, PARK
- electric power transfer, alt 1, alt 2 = ON
> HYD.S, PARK
========================================================= METHOD 2
-(?) main battery = ON
> audio warning
- audio warning reset
> TRN, HUILE, B.P, BP.G, BP.D, HYD.1, HYD.2, HYD.S
** error: ALT1 and ALT2 lights should be ON
- parking handle raised
> TRN, HUILE, B.P, BP.G, BP.D, HYD.1, HYD.2, HYD.S, PARK
- vent/ignition on D or G
- engine fuel pump L and R ON
> HUILE, HYD.1, HYD.2, HYD.S, PARK (-B.P, BP.G, BP.D)
** error: B.P light should be ON
** actually, B.P switches off when either BP, engine fuel L or R is ON
- either starter pump ON, or open the engine start cover
- wait for B.P OFF
> TRN, HUILE, HYD.1, HYD.2, HYD.S, PARK
- click on engine start for 1 second
- wait for N >= 10%
> TRN, HYD.1, HYD.2, HYD.S, PARK (-HUILE)
- throttle on idle
> audio warning at N=20%
- audio warning reset
> Tt7 climbs to 800 °C
> N to 75% and aircraft moves forward ~50 cm
> N down and stable at 49
> Tt7 down and stable at 650 °C
> ALT1, ALT2, TRN, HYD.1, HYD.S, PARK
- electric power transfer, alt 1, alt 2 = ON
> HYD.S, PARK
========================================================= METHOD 3
- main battery = ON
> audio warning
- audio warning reset
- electric power transfer, alt 1, alt 2 = ON
> HUILE, B.P, BP.G, BP.D, HYD.1, HYD.2, HYD.S
- parking handle raised
> HUILE, B.P, BP.G, BP.D, HYD.1, HYD.2, HYD.S, PARK
- vent/ignition on D or G
- engine fuel pump L and R ON
> HUILE, HYD.1, HYD.2, HYD.S, PARK
** error: B.P light should be ON
** actually, B.P switches off when either BP, engine fuel L or R is ON
- either starter pump ON, or open the engine start cover
- wait for B.P OFF
> HUILE, HYD.1, HYD.2, HYD.S, PARK (-B.P)
- click on engine start for 1 second
- wait for N >= 10%
> HYD.1, HYD.2, HYD.S, PARK (-HUILE)
- throttle on idle
> ALT1, ALT2, TRN, HYD.1, HYD.S, PARK
> audio warning
- audio warning reset
> Tt7 climbs to 800 °C
> N to 75% (aircraft does not move)
> N down and stable at 49
> Tt7 down and stable at 650 °C
> HYD.S, PARK
-
Yep, written text is subject to interpretation, sometimes makes for awkward ones. Short questions like "are you serious?" invite to human's defence mechanisms embedded for thousands of years ;) So if it's an actual question out of interest, it's probably best to read it from the other's point of view and maybe worth explaining a bit more :)
The aircraft is made of multiple parts, one of them being the flight model. This one is coming from J.M. Langeron ("Topolo", see http://topolo.free.fr/news.htm but this site hasn't been updated in a long time since its V5 flight model AFAIK), who iterated and collected data / feedback from many people, but except allusions to leaked data, I never saw anything "official" - and I would be surprised to see anything, given this is still secret material.
There's another model from Bernt Stolle, used in the Metal2Mesh's M2k with inputs from "3 pilots, 2 mechanics and former FAF officers"... whatever that means. It would be interesting to compare both (and it has probably been done when those models were adjusted).
So it is as good as it gets until the FM is declassified. Anyway you only have a limited interface with the virtual world in which these aircraft fly: a joystick, rudder pedals, maybe a throttle, TrackIR or even a VR helmet... Still, you're far from the real experience, I'm not sure it's worth questionning whether those charts are 0.1% or 0.05% accurate, for me it's enough to know they have been validated for years by many knowledgable people.
jojo surely knows a lot more about this, but given how the thread started I'm not sure he'll come back and explain - once more, the fine details behind this model... that's probably why it's worth engaging in a conversation... let's say, more smoothly.
-
In DCS 1.5.2.48726.137 (and DCS 2.0.0.48763.61):
- ruler is visible again!
- names are still very hard to read, another typical example below where it's almost impossible to see what is what, even when zooming in (here it's not the airport name but mostly the airplanes / other objects).
Suggestions:
- different colours / outline as in the mission editor,
- selection of which names to display with for ex. icons on the border of the screen,
- layer pop-up / enhancement of what the mouse if hovering,
- more difficult to implement, labels that are scattered to have enough room to be displayed, with an edge pointing to their object.
-
Hello,
I noticed that the longitude was missing when clicking on an entity, in the map view, only the latitude is shown. Quite annoying for instance if you need to align an aircraft manually, or get the coordinates of some object/target/destination.
The problem can be reproduced in the following versions:
- DCS 1.5.2.48726.137
- DCS 2.0.0.48763.61
You can check the mouse coordinates as a temporary work-around, but it's not very practical, nor precise.
-
This is exactly the point.
Angry comments are just like the people who write them, USELESS. I'd love to reply to some very clever and helpful guys like Doctor Nonsense, but i'm not in the mood for easy trolling, especially when it comes to casual users.
Let me just apologize in advance for all the keywords you are gonna read in this reply, but apparently some fundamental aspects are being overlooked.
Dear Zeus, you are missing something here... Maybe it's because you are kinda new to the game of developing and supporting your own product or maybe it's just bad attitude. BMS publish free content, top quality content, but the keyword is FREE.
We are paying customers here, keyword is $$$, and the game you decided to throw yourself in is called simulation, a pretty "real world data" thirsty enviroment. Noone is talking trash about your work (although i COULD complain because i PAYED for this product), we are just asking for information about the product we bought (sorry to remind it again, but you are not BMS). Getting customers frustrated because you didnt like something someone wrote about your product, is not a good strategy. Less is more when you cant really answer something in a proper way with solid data backing up your answer, especially when there is money involved.
People is happy about the mirage? Good for you, i like it too, but you need to provide as much data as you possibly could, clear and concise explanation of what and how not emotion driven answers. Otherwise you could simply choose not to answer this kind of topics and enjoy the posts from the people that aren't worried because "the flying is fine" and "everything will be perfect once the beta ends".
Last but not least, good attitude keeps customers satisfied, a satisfied customer is a returning customer.
I'm done, i'm leaving space for the fanboys to flame this topic while we won't get any answer because some guy from BMS already did all the work and is absolutely perfect and great and the cyrillic version is somehow CLOSE to what we bought.
Wow...
I have a different point of view on this.
Please read it again, Zeus' answer was to the point, he must be quite busy and he actually bothered to answer what is unquestionably a troll's question, to me it was very well handled and showed more cool than most of us would have had. jojo's reply elaborated on the concerrn once the OP finally expressed himself in a more, if barely polite, understandable way. Job done.
IMHO, making a fine product doesn't mean you have to prostrate yourself before such rude behaviour, it's not as if we were talking about selling potatoes. The product we are talking about has a reputation of its own and that is what sells, not the quality of the vendor's smile when he faces angry kids.
Besides, the tone has to be set, you wouldn't want this to become the norm here ;)
-
Thread Bump.
Still a few items.
pp. 78, "DCS (Données Codées Inertielles)" --> "DCI".
Checklist, pp. 71:
- don't we need to switch the battery on as 1st step? (or require and use ground power?)
Engine start, pp. 72:
- as such, I see HYD.1 is ON after step 10, only switches off when I'm switching on batteries and power supplies. Is it normal?
- missing step: switch off Starter Fuel Pomp, Ignition/Vent on "Vent" (once engine idle at 48%?)
Parking (shutdown?), pp. 74-75:
- do we have to press on the engine shutdown button (left console)? Is there an equivalent to the throttle "STOP" position?
-
Not sure about what happened next, but the engine shutdown button is on your left, the red button (marked 35 pp. 14 in the manual).
I don't see it in the parking checklist though.
-
Actually for me it's the only aircraft for which I don't have to invert the brake axes, with the Saitek Pro rudder pedals.
-
Haha, yes, I saw that. I took the picture of the pilot, but he didn't seem pleased.
DCS version 1.5.2.48726.137.
This happens in the "Cold Start" instant mission, one of the two AI Mirage 2000 crashes into a jeep after landing - so you have to wait for those two jets to take off (at the beginning of the mission), to fly through their waypoints and to land before witnessing the accident. The pilot ejects and lands a little further, the other jet stops normally and opens the canopy but its pilot doesn't get out.
How to navigate in the Mirage
in M-2000
Posted · Edited by Redglyph
Hydraulic circuit 1 is for the brake, among others (and circuit 2 for the emergency brakes, among others). There's an HYD.1 warning lights for this one (pression < 195 bars), and a double gauge at the base of the stick, on the left.
EDIT
Still OOT, but I seem to get some degree of control over the brakes, other than all-or-nothing. You can see it by braking left / right, you can control the steering depending on how much you push on the brakes.
The gauges don't work though, they remain at zero.