Jump to content

Recommended Posts

Posted
@baltic dragon

Would it been possible to go for font which is not as narrow (vertical stretched)? The sample is very hard to read.

 

Otherwise I look forward to the complete manual...

 

+1.

 

I would prefer a proportional space font like Times or Arial, and ideally a font that everybody has (like Times or Arial) so that the font isn't rasterized when zooming on a page.

  • Replies 310
  • Created
  • Last Reply

Top Posters In This Topic

Posted

Nice work, I really like it!

 

But - if it is not too late - maybe you would like to consider changing the way the elements in the pictures/hardcopies are numbered. As it is in these sample chapters, the numbering is somewhat hard to read. I actually like the ED way - numbering outside of the pic and arrows/lines connecting them to the cockpit elements. But if that is not viable, at least make the numbers stand out a bit more? Put a circle around them, use a deliberately (and consistent) highly visible colour?

Posted
I actually like the ED way - numbering outside of the pic and arrows/lines connecting them to the cockpit elements.

Agree. I`d say numbers on the first page of the fuel chapter are much more readable.

m2000fuel.PNG.ab59d671de62827be32de8254899d4be.PNG

It is great to see a progress on the module, thank you!

Posted

It needs to be something in between if they are going to be changing this at all. ED way also can get confusing when there are a lot of numbers it become a mess of lines which you have to follow to see what is what :)

[sIGPIC][/sIGPIC]

Posted

LOL I will stop posting stuff otherwise I will spend my whole time backtracking and updating things I have already done ;)

 

Joking. In facts sometimes I am using old pics from original manual, especially where there is no way to get a good screenshot angle. But some of them are outdated with new switches etc added to the pit so I have to replace them. Sometimes it is better to see parts of the pit against the background of other instruments etc. I'll do my best to make it easily readable and looking good at the same time.

 

Started working on HUD and I am sure I will use colour screenshots against some nice Nevada background.

For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel.
Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.

Posted
LOL I will stop posting stuff otherwise I will spend my whole time backtracking and updating things I have already done ;)

 

Joking. In facts sometimes I am using old pics from original manual, especially where there is no way to get a good screenshot angle. But some of them are outdated with new switches etc added to the pit so I have to replace them. Sometimes it is better to see parts of the pit against the background of other instruments etc. I'll do my best to make it easily readable and looking good at the same time.

 

Started working on HUD and I am sure I will use colour screenshots against some nice Nevada background.

I am not sure I understand what you are refering to ... if it is about our request regarding the screenshots, then there might be a misunderstanding.

 

At least what I meant was, the numbering of the elements of a screenshot does not stand out enough. For example, at first, I did not even saw that there were numbers added to the fuel gauge. The white numbers looked almost as were they part of the instruments labelling. Finding a specific element by number, i.e. when reading the description text, is somewhat difficult.

 

So, it is not about the screenshots itself, or any surrounding scenery, it is just simply the numbers added for referencing the switches and gauges. It would probably already help alot, if they would stand out more by using a bright (red?) colour and/or graphically (framing them into a circle or something like that) to make clear, that they are not part of the actual cockpit labels.

 

edit:

But if you say, you would have to redo all your pictures and that this would be an insane amount of work ... I would totally understand that. But if it is NOT too late, then, well, maybe something could be done here. ;-)

Posted
Sometimes it is better to see parts of the pit against the background of other instruments etc.

I think left "4" could be an option:

m2000fuel2.PNG.a3998dc4dde7be4520a7d80c031dfb5d.PNG

Posted
I am not sure I understand what you are refering to ... if it is about our request regarding the screenshots, then there might be a misunderstanding.

 

At least what I meant was, the numbering of the elements of a screenshot does not stand out enough. For example, at first, I did not even saw that there were numbers added to the fuel gauge. The white numbers looked almost as were they part of the instruments labelling. Finding a specific element by number, i.e. when reading the description text, is somewhat difficult.

 

So, it is not about the screenshots itself, or any surrounding scenery, it is just simply the numbers added for referencing the switches and gauges. It would probably already help alot, if they would stand out more by using a bright (red?) colour and/or graphically (framing them into a circle or something like that) to make clear, that they are not part of the actual cockpit labels.

 

edit:

But if you say, you would have to redo all your pictures and that this would be an insane amount of work ... I would totally understand that. But if it is NOT too late, then, well, maybe something could be done here. ;-)

 

I'm agree with you.

From my point of view, the Belsimtek F-5E manual is a reference. The numbering of the elements of screenshots are very clear :smartass:

The communications Controls Arrangement is on page 133 of the manuel.

Current specs: Windows 10 64bit, i7-7700K @ 4.8 Ghz, 32 GB RAM, 1 To SSD, RTX2070-Super, TrackIR 5, TM Warthog, TM T.Flight Rudder Pedals

Posted (edited)

I understood perfectly well what it was about - and wherever able I will make sure to change it (should be in most cases). My comment was just a joke about the feedback and changes I will have to make in general (different font, different numbering etc) - but hey, I am not doing the manual for myself, so I'd rather put in some more work and make more people happy ;)

 

Thanks for all the comments and feedback guys!

 

EDIT: is the attached more or less what you were talking about?

719950083_10-3HUDgeneral.thumb.jpg.157bec659513bca66350a402c1c46ddc.jpg

Edited by baltic_dragon

For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel.
Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.

Posted

Great work Baltic_Dragon!

 

I've spotted one mistake though, probably from a copy/past, on the V/UHF and UHF radio panel overview :

Knob #6 : UHF OPERATION MODE SELECTOR. The five-position AR, PAL, PAL + G, FI, H function selector switch determines the radio operating mode:

AR: (Arrêt) OFF. No power is applied, the bottom row of RADIO FREQUENCY DISPLAY remains blank.

M: (Manual). Main frequency. Power is applied and the main preset frequency is used.

FI: Not used.

H: Not used.

Those operation modes concerns the Knob #11 V/UHF Rx Mode Selector. The right modes are, as explained, AR, M, FI, H.

 

Keep it up bud!

Posted (edited)
is the attached more or less what you were talking about?

yes.gif

Is it possible to specify "NOT FUNCTIONAL" features which of them will be implemented and which will not due to DCS platform limitations?

Edited by azm
Posted
Great work Baltic_Dragon!

 

I've spotted one mistake though, probably from a copy/past, on the V/UHF and UHF radio panel overview :

Those operation modes concerns the Knob #11 V/UHF Rx Mode Selector. The right modes are, as explained, AR, M, FI, H.

 

Keep it up bud!

 

Thanks, corrected!

 

yes.gif

Is it possible to specify "NOT FUNCTIONAL" features which of them will be implemented and which will not due to DCS platform limitations?

 

I have the NON-FUNCTIONAL label that I am sticking to various systems and instruments that I know are not working, though I have no way of telling precisely which will be working in the future. So whenever I find something that is not implemented or working properly I just label it as "non functional". For the things I am 100% they will be done, I label them "Non functional yet".

For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel.
Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.

Posted
For the things I am 100% they will be done, I label them "Non functional yet".

This is exactly what I mean, thanks!

Posted

performance chart

 

Thx 4 updating the "problem child!

I'm missing turn performance chart of my lovely M-2000C.

TurnPerformance.thumb.jpg.ed10e0b72fad8df5061fe216497df475.jpg

Bullseye-Training

Hardware: TrackIR5 | Buddy-Fox UFC | TM Warthog | Saitek Pro Flight Rudder Pedals | i7-4790k | GTX 980 | 32GB RAM

Modules: F/A-18C | A-10C | M-2000C | F-5 Tiger II | UH-1H

Posted
Thx 4 updating the "problem child!

I'm missing turn performance chart of my lovely M-2000C.

 

We will add the charts once we have the updated FM out - so we will use data from the sim in order to reflect in 100% what the simulated M-2000C is doing. No point in adding that beforehand!

For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel.
Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.

Posted

This is gonna be cool!

Gigabyte Z390 Gaming X | i7 9700K@5.0GHz | Asus TUF OC RTX 4090 | 32GB DDR4@3200MHz | HP Reverb G2 | TrackIR 5 | TM Warthog HOTAS | MFG Croswinds

Posted

Hey guys, a small update: The HUD section is now ready, that was a big one to update - 26 pages in total with lots of screenshots. Moving on to another huge topic - NAV system.

 

Also, as a side note, the following parts of the manual are now done or mostly done: Introduction, Aircraft Basics, Instruments list, Engine, Electrical System, Fuel System, Hydraulics, Mobile Surfaces, Fly By Wire, Autopilot, Trim System, Landing Gear, Avionics: HOTAS, Flight Instruments, Radios, VOR and TACAN.

 

The manual is coming nicely together, thanks for all the tips on how it should look like!

For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel.
Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.

Posted

Good news :)

Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil WarBRD, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...