Re: Days Gone Pc Cheat Engine Table

1 view
Skip to first unread message
Message has been deleted

Floriana Monterroza

unread,
Jul 13, 2024, 5:45:25 PM7/13/24
to bunghearsapphub

Articles should always be named as generally as possible using the common name except for engines with United States military designations. US military designated engines should use the designator and not the name. If more than one engine has the same name then a suffix should be used for the least common engine, for example Rolls-Royce Trent (turboprop).

days gone pc cheat engine table


DESCARGAR https://bltlly.com/2yOKFz



I have filled in some of the sections with initial advice, hope it is sensible and not too draconian, feel free to 'tweak' as required! What would be very useful is to promote one engine article to FA to use as a 'benchmark', it would be a WP first and a great achievement. Must repeat many thanks to RL for setting this page up. Nimbus (Cumulus nimbus floats by) 03:27, 12 December 2008 (UTC)

Some engine articles have two sets of specifications, like the Junkers Jumo 205. Is this necessary or desired? The second set of specs in this article are for the Junkers Jumo 204 (redirects to 205), a very similar engine with a different displacement (and presumably different applications). Perhaps it is a sign that a new article is needed in this particular case. Nimbus (Cumulus nimbus floats by) 02:01, 13 December 2008 (UTC)

Just an idle thought, the engine articles don't have a 'survivors' or equivalent section. Would we want to include this section or are the articles better without it? I don't think that we would end up with large lists seen in some of the aircraft articles. I have seen one article with an 'incidents and accidents' section which could be fair if the accident was directly caused by an engine failure and it was referenced. Nimbus (Cumulus nimbus floats by) 19:01, 13 December 2008 (UTC)

Would there be any interest in having a variant article for the Packard V-1650? There is an awful lot of info on the Packard-built version on the Rolls-Royce Merlin, much of it choppy, poorly written, and contradictory. I think splitting off and rewriting this info would help to better streamline the RR Merlin page. It's my unferstanding that the Packard-built Merlins differed quite a bit from the British versions, and thus probably do warrant a separate page, and we do often cover foreign license-built aircraft separately, and probably some engines too. Thoughts? - BillCJ (talk) 02:01, 15 December 2008 (UTC)

Some of the aeroengine articles, such as Bristol Centaurus, have the Applications section after the Specs rather than before it. As such, it comes right before the See also section, which might not be a bad idea. Following RL's recommendation to consider "in the wild" formats, is this a better format, or does it work best after Variants as suggested in the guidleines. (The latter format is what I have been following.) - BillCJ (talk) 12:36, 17 December 2008 (UTC)

Another idle thought (I have lots of them!). Should we publicise the engine project on the main 'aviation' and 'aircraft' talk pages? The tab has appeared and there is a short line on WT:AIR but it might not be obvious that a new sub-page has started. Nimbus (Cumulus nimbus floats by) 21:40, 17 December 2008 (UTC)

As far as I can tell, Mercedes was owned by Daimler when the aeroengines were produced. When Daimler merged with Benz in 1926, the aeroengines were then produced under the Daimler-Benz name. Shoukd we perhaps merge Template:Daimler-Benz aeroengines and Template:Mercedes aeroengines? This is how several other smaller templates of merged companies are handeled, such as Template:Garrett/Honeywell aeroengines. Also, Curtiss' and Wright's separate aeroengine businesses were merged in 1931 under Wright, so it's possible we could merge Template:Curtiss aeroengines and Template:Wright aeroengines too. Just asking. - BillCJ (talk) 02:35, 19 December 2008 (UTC)

(undent) When we were busily implementing navboxes earlier this year, I noted the problem of navbox proliferation on types like the Beech 18. The solution would be to make the navbox collapse in groups; so that if there were more than (say) 3 designation boxes they could collapse together into a "Designations" navbox, and if there were more than (say) 3 manufacturer boxes (starting to happen on aircraft built under licence by a number of firms), then these would collapse together into a "Manufacturers" navbox. It's definitely do-able, so since the issue's come up, I'll get to work on it!

FWIW, the USN navboxes are long by design. This designation system seems to cause a lot of confusion, due to it being counter-intuitive to those who've never been on familiar terms with anything but the USAF-style designations that became the norm after 1962. This was painfully obvious when replacing the old "sequence" parameters in the "see alsos" of Navy aircraft articles. By explicitly splitting the manufacturer codes to their own lines, I hoped it would be clear that, for example, F4B is not followed by F4C, but by F5B! That being said, if anyone can think of a way of ensuring that point is made, while reducing the overall size of the box, I'd certainly be glad to hear it. --Rlandmann (talk) 03:08, 20 December 2008 (UTC)

RL, would it be possible to combine the functionality of Aeroenginecontent into Aircontent? The only divergent field is "similar engines". This would simplify the use of the See also section templates within WP:AIR, and enable all changes and tweaks to be made to just one template. Currently, Aeroenginecontent is used in less than 50 articles, so converting them to Aircontent now should be simple and easy. I know you're busy, so I don;t expect it to be done quickly, assuming it can be done amd that WP:AIR wants to do it. Thanks. - BillCJ (talk) 04:10, 20 December 2008 (UTC)

A quick look at some of the British aircraft rocket engines reveals some problems that need fixing. The Bristol Siddeley Gamma is interesting with multiple infoboxes and the 'commons link' at the top of the article. I stacked Infobox Aircraft Begin above Infobox rocket engine in de Havilland Spectre to tidy the image position but this is causing code/display problems with the lower infobox. There was a short discussion about the 'non-standard' rocket engine infobox here: [1]. I don't believe that we have a Template:rocketspecs for specification sections which makes it harder to tidy these articles. Some of these engines were not used in 'aircraft' as such and may fall under the rocketry project (if there is one) but I am willing to have a go at tidying them given the right templates. Thoughts? Nimbus (Cumulus nimbus floats by) 14:33, 21 December 2008 (UTC)

I just ran across the Walter Aircraft Engines article, which is suprisingly good, though it needs more citations. However, en.WP does not have an article on the Walter M601, arguably Walter's most significant engine. The only interwiki article on the M601 is at de:Walter M601, on the German WP. It seems to be a fairly good article, and while it has no citations, it does have a few ELs. I'll try to check my Gunston in the next few days, and see if it has enough to start a page, along with GE's page on the M601H-80 variant. There are two M601 images on Commons, one of which is in the German article. If someone could look at the German page, and perhaps do some translation work, that would be a great help. Thanks as always. - BillCJ (talk) 09:57, 25 December 2008 (UTC)

While checking links to the new Walter M601 article (see above; and thanks Bill - one that's been overlooked too long!), I came across a large number of links to this and to other Walter engines that had been broken by piping them to the article on Walter Engines (ie, by doing this: [[Walter EnginesWalter M601]]), presumably in an attempt to avoid a redlink. Most of these were the work of a lone contributor, but a prolific one who seems to have done this kind of thing quite systematically.

When creating new engine articles or doing significant work on existing ones; it's worth checking the "what links here" on the manufacturer's page to try and identify this kind of pipe problem. I've seen more than one contributor doing this. There are few articles on aircraft types that need a link to the manufacturer of their engines; any that show up in the manufacturer's "what links here" should normally warrant further investigation. --Rlandmann (talk) 09:41, 26 December 2008 (UTC)

It's all happening and I am struggling to keep up! I noted that we had not added US military piston aeroengines to all the articles yet and there is the odd redirect in there which needs fixing. I was a bit hesitant with it around some of the general aviation engines like the Lycoming O-360 and have not added it. It looks like some of those engines were not used by the military? Can't be sure. Nimbus (Cumulus nimbus floats by) 18:37, 1 January 2009 (UTC)

I am posting this here instead of the article talk page for wider coverage. I have never heard of this term and can find no reference to it on the internet or in books. This article is four years old with no references, is that a WP record?! I fear that it is all original research but stand to be corrected. Nimbus (Cumulus nimbus floats by) 21:29, 1 January 2009 (UTC)

There is a discussion ongoing on the Merlin talkpage [2] concerning how (and how many) power outputs are given in an engine article. All friendly stuff, I just want to check that I am on the right lines with how we deal with this potential problem. Cheers Nimbus (Cumulus nimbus floats by) 14:10, 9 January 2009 (UTC)

I created the Pratt & Whitney R-2180 page today, but have since found some information that is somewhat conflicting. Some sources state that the R-1280 was the Twin Hornet, and it was used on some designs in the mid-30s, notably the Douglas DC-4E. On the other had, there appears to have also been a R-2180-E Twin Waps E, which used the cylinders of the R-4360, and was used in the Saab 90 Scandia. Are these 2 versions of the same basic engine, or 2 differnt ones witht he same displacement? Btw, the Saab 90 Scandia ariticle could use some work to bring it inline with the WPAIR page content guidenlines, but I'm hesitant to modify it myself, as much of the work was doene by a user I've had "ownership" problems with before. - BillCJ (talk) 21:43, 21 January 2009 (UTC)

d3342ee215
Reply all
Reply to author
Forward
0 new messages