Selecting Reach vs. HiDef

re: Selecting Reach vs. HiDef

anonymous13 — Fri, 31 May 2013 15:28:30 GMT

can anyone tell me how can i change profile?

re: Selecting Reach vs. HiDef

Mati Rehman — Fri, 21 Dec 2012 16:16:54 GMT

Thanks for the help , worked for me :)

re: Selecting Reach vs. HiDef

unknown — Tue, 03 Jul 2012 15:41:51 GMT

hello! when i did it after the program show me an other error....

that: No suitale graphics card found.

Unable to create the graphics device.

please answer me How can i fix it!

tnx.

sorry bad english. ;-)

re: Selecting Reach vs. HiDef

Anon — Wed, 18 May 2011 18:04:03 GMT

I'm sorry but I'm really starting to rage at this.. Y.. I don't have this interface. All I'm trying to swap the thing so it'll run a certain popular game going about. Nor do I see any connection between this and any programme in the XNA game studio programme folder.

re: Selecting Reach vs. HiDef

Team TFE — Wed, 04 May 2011 05:48:23 GMT

It'd be nice if there was a way to get the fatbat's hack functionality officially added. I.e. we should be able to develop for hi-def on a non compliant machine as an option. My card is fully capable of everything required by hidef except two (unused) requirements. Since I'm devloping for xbox360, it's frustrating to be artificially limited by the dev machine rather than the final platform. You're basically forcing us to release a lower quality game due to this limitation, which is a lose-lose for everyone.

re: Selecting Reach vs. HiDef

Niinii — Sun, 03 Apr 2011 13:12:09 GMT

Thanx you little bit help me ^_^

re: Selecting Reach vs. HiDef

Shawn Hargreaves - MSFT — Mon, 31 Jan 2011 03:28:45 GMT

Bela: this error means that whatever project you are using to build these .xnb files is set to HiDef as opposed to Reach profile, in its Visual Studio properties.

btw. I would recommend the create.msdn.com forums for getting help with issues like this: that's a better place than blog comments for tech support discussions!

re: Selecting Reach vs. HiDef

Bela Kampis — Sat, 29 Jan 2011 22:12:15 GMT

Hi Shawn, first off great blog, I`ve been using it a lot to help me develop this WPF + XNA 4 game I`m working on. I`m having a problem with xnb files copied over from one content project to another.

What I needed to do was select the Reach profile because the game has to run on a fairly old set of Dell laptops that have very limited GPU capabilities. Thus I have to modify all my textures to use power of two sizes and rebuild them. I can now load the textures fine in a test project that I use just to validate the graphics device can handle the textures and load them properly, but when I copy over the folder of all these .xnbs to my game folder, each time I try and use the content manager via a Reach profile to load one of the textures, it says they are still created for a Hidef profile and I am in Reach. I don`t understand at all what`s happening. When I run the game in hidef with the hidef-built versions on my desktop, it can load the textures fine and I don`t need to limit them to power of twos or 2048x2048 sizes. The exact same code keeps throwing these exceptions, saying that I should be loading these resources in Hidef when I rebuilt them and they load fine in Reach via a real Game-based XNA project.

Any ideas?

My exact exception is :

{Microsoft.Xna.Framework.Content.ContentLoadException: Error loading "_____". This file was compiled for the HiDef profile, and cannot be loaded into a Reach GraphicsDevice.

at Microsoft.Xna.Framework.Graphics.GraphicsContentHelper.GraphicsDeviceFromContentReader(ContentReader contentReader)

at Microsoft.Xna.Framework.Content.Texture2DReader.Read(ContentReader input, Texture2D existingInstance)

at Microsoft.Xna.Framework.Content.ContentReader.InvokeReader[T](ContentTypeReader reader, Object existingInstance)

at Microsoft.Xna.Framework.Content.ContentReader.ReadObjectInternal[T](Object existingInstance)

at Microsoft.Xna.Framework.Content.ContentReader.ReadObject[T]()

at Microsoft.Xna.Framework.Content.ContentReader.ReadAsset[T]()

at Microsoft.Xna.Framework.Content.ContentManager.ReadAsset[T](String assetName, Action`1 recordDisposableObject)

at Microsoft.Xna.Framework.Content.ContentManager.Load[T](String assetName)

at _______.TextureManager.LoadAlphaTexture(String path) in ____________________.cs:line 182}

I did a search for any files containing hidef and it looks like the default content importer assumes a HIdef graphics interpretation unless Reach is explicitly stated. So that if you aren`t using a Content pipeline reference in your project and just instantiating a ContentManager in code, it will throw this type of exception. Is there a way to set my content manager to interpret the XNB files as they truly are, i.e. compiled as Reach? I can`t figure it out.

re: Selecting Reach vs. HiDef

MichaelT — Thu, 12 Aug 2010 09:34:05 GMT

Never mind, I found it:

graphics.GraphicsProfile <- GraphicsProfile.HiDef

It is a case of "finding it when you no longer need it" :)

re: Selecting Reach vs. HiDef

MichaelT — Thu, 12 Aug 2010 09:29:56 GMT

I would be a very happy camper if someone could tell me how to get a hidef graphicsdevice using F# and XNA. I got everything to work with F# and XNA except that. Is it even possible?