From Valve Developer Community
Jump to: navigation, search

What does VMF stand for? File or Format?

I thought VMF stands for Valve Map File. Whats right? --King2500 07:34, 8 Sep 2005 (PDT)

Jeff Lane can probably clarify but I believe it is format as file would be redundant. --wisemx 08:55, 8 Sep 2005 (PDT)
How is it called in Hammer's open-file dialog? --King2500 09:41, 8 Sep 2005 (PDT)
File open is Valve Map Files (*.vmf), which they are, however that doesn't clarify it.
You're still opening Valve map files no matter what the "f" stands for.
Opening Valve Map Format files. vs. Opening Valve Map Files files. --wisemx 10:28, 8 Sep 2005 (PDT)
I think Autolycus or Jeff can clarify this. --King2500 10:58, 8 Sep 2005 (PDT)
Yes indeed. ;-) --wisemx 11:35, 8 Sep 2005 (PDT)

Okay, I'm nearly at the stage I'm going to upload my information, its more a Technical file rather than a Glossary defenition So I will be placing it there. After I'm done I'm going to re-rite this and link to there. --Angry Beaver

This still hasn't been resolved. Angry Beaver originally wrote the VMF documentation article, claiming that VMF stands for Valve Map Format. ts2do made the change to the VMF article, claiming the VMF instead stands for Valve Map File. Is there any more evidence for either case? I heard that you can look into the .h files of some file types, and find the acronym explained there. That would help greatly. (Note that VTF stands for Valve Texture File, so it's definitely possible that that is the case.) --Andreasen 02:24, 7 Sep 2007 (PDT)

I wrote it as format because thats what I thought it was, at the time I wasn't aware of any ambiguity regarding its meaning. I'd suspect it'd be file as A that makes sense and B ts2do generally knows what he's talking about. give me time to finish reinstalling VS 2005 before I go looking in the .h files though, just did an OSRI. --Angry Beaver 13:10, 8 Sep 2007 (PDT)
This all seems a little pointless. Besides, doesn't ts2do work for Valve? Hence, doesn't his change specifying VMF as Valve Map File allow us all to just go "Oh.. okay..." --Kal Esh 18:48, 8 Sep 2007 (PDT)
Also, shouldn't VMF documentation be merged into VMF. At least that way we only have to go to one place to find out about everything. --Kal Esh 18:48, 8 Sep 2007 (PDT)
ts2do does not work for valve as far as i can see, his user page doesn't have the valve stamp nor is it on the valve employee list. As for who cares, not me. As for merginn, no. Look at VMF documentation its huge, sometimes it even gives you wanring messages about its size and for 3/4 of the people out there its not important info. Just a link inside the VMF page is good enough IMHO, despite the facts its kinda addicting to see how many views I can get on all the articles I write :) --Angry Beaver 22:36, 8 Sep 2007 (PDT)
No, while he is very dedicated to this wiki, ts2do doesn't work for Valve (I believe the most frequent Valve employee is Jeff Lane.), and on occation he also makes editing decisions I find weird, so we should trust the .h file more than we trust his mere word. Why it's important is because I'd like to start writing "Valve Map Frog(?)" instead of "VMF", so that people don't confuse it with VTF or VMT or other abbreviations. Abbreviations makes these terms harder to recognize, at least for newbies. --Andreasen 05:03, 9 Sep 2007 (PDT)
Ah, well I guess I'll take a look at Jeff Lane's page to see this "official stamp." (Unless he doesn't have one?) I understand the need for correct terminology, with more than one acronym starting with V it can be hard to recognize for newcomers which is which. Speaking of the .h file... what does it say? --Kal Esh 11:31, 9 Sep 2007 (PDT)
As this still has not been resolved (after over three years), I'm stating this ambiguity in the article itself. --MossyBucket (formerly Andreasen) 14:04, 13 February 2011 (UTC)

Merge with Article "VMF documentation"

I think this Article should be merge with VMF documentation. This Article is very short and can be included in Vmf documentation. Then the User can easy see all informations on one page. Anyone thinks so too? --Dmx6 09:18, 22 November 2011 (PST)

I think those two articles should stay separate. The vmf article is intentionally short because its purpose is to inform users about the general properties of a vmf file. On the other hand, the vmf documentation has lots of in-depth information that will not be of any use for the majority of users. As such I think a link as given at the bottom of the vmf article page is the right solution. --Innocentive 23:40, 6 February 2013 (PST)