I'm running the Windows Phone 7 dev tools on an older MacBook Pro, with an NVIDIA GeForce 9400M graphics card with 256MB of memory (not sure if it is shared or not) and I get lots of stuttering in the animations on the emulator, even simple ones, so I assume that it's not using my graphics hardware. The framerate counters are always at something like 002 or 003 (and red).
According to this post on the Windows Phone forums, these are the requirements:
"DirectX 10 capable card with a WDDM
1.1 driver is needed to take advantage of GPU acceleration on the Windows
Phone Emulator for a Silverlight® application"
From running DxDiag, my card supports DirectX 10 and WDDM 1.1, I've installed the latest download of the tools from create.msdn.com, and the latest drivers from NVIDIA.
This is happening on a clean install of Windows 7.
I was able to run an empty XNA Windows Phone game without the error message mentioned here, so maybe it is using hardware acceleration after all, but the normal Silverlight stuff is really jerky.
What can I do to get the emulator graphics to run at a decent speed?
You should check this post
Related
I have a Dell PowerEdge T430 running Fedora 25. It comes per default only with onboard graphics (which allows only a resolution of 1024x768 (at least I was not able to get any drivers running) and is insufficient for some applications that produce graphical output).
I bought a Geforce210 graphics card and plugged it in but how do I tell Fedora to use it instead of the onboard graphics?
Pretty sure you need to do this in the system's own System Setup ("BIOS configuration") — go to the Integrated Devices section and switch Embedded Video Controller to Disabled. I don't think there is any support for multiple video controllers to be active at the same time.
please help
I've been trying to set up kinect for XBOX 360 to run on ubuntu in order to start developing an application to control a humanoid robot. for the past four days I've been searching , downloading , installing and trying dozens of libraries and drivers to get the kinect to work on Ubuntu. in the beginning none was working and I was only able to read the RGB camera with "Camorama" and "guvcview" no matter what library or driver I attempted to run.. Finally, I installed a fresh copy of Ubuntu and installed libfreenect libraries using synaptic (I'm kinda newbie) and I also installed the following packages
https://code.google.com/p/simple-openni/downloads/detail?name=OpenNI_NITE_Installer-Linux64-0.27.zip&can=4&q=
along with Processing 2.0 and SimpleOpenNi-0.27
I start Processing -> examples -> OpenNi -> DepthImage & RUN
and the kinect starts for 3 to 10 seconds giving the image below some times along with the RGB image and some times with out it, then the frame freezes, and when I try listing the USB devices ($lsusb) there is no Kinect camera or audio devices listed, so the Kinect must be unplugged from the Adaptor and USB and then re-inserted and the problem still occur after running the sketch.
Attempted solutions:
1- removing and black listing gspca kernel module
2- disabling USB auto-suspend
but the problem still occur...
I'm using Kinect for XBOX 360 with (12V - 1.08A) USB AC Power Adapter
http://www.walmart.com/ip/INSTEN-USB-AC-Power-Adapter-For-Microsoft-Xbox-360-Kinect-Sensor/28882271
My laptop is : DELL Inspiron.1525 Intel Core2Duo RAM 2GB
Running Ubuntu 14.04.2 LTS ,, Release: 14.04 ,, Codename: trusty
Can any one help me please!!.
I had a similar problem and after I used Kinect With windows, I found that the problem was from the Kinect itself.
The following tips will help you get started using your Kinect:
If a non-Microsoft driver for the Kinect is installed on your computer, the Kinect for Windows drivers might not install or function correctly. To fix this, uninstall the non-Microsoft drivers before installing the Kinect for Windows SDK.
Connect the power supply for the Kinect to an external power source; if the Kinect has only power from the USB connection, it will be minimally functional and light the LED, but it must be connected to an external power source to be fully functional.
No tools are required for calibration of audio and video.
Your Kinect should be the only device plugged into a USB hub on your computer. If you have more than one Kinect, connect them to different USB controllers. If 2 hubs are connected to the same controller, only 1 Kinect can work at a time.
The Kinect is protected from overheating by a fan. It is controlled by the sensor's firmware, which turns off the camera at 90 degrees Celsius. There is no software interface for applications to control the fan.
Reasonable lighting, neither extremely dark nor extremely bright, is important for capturing images with the RGB camera. Incandescent, fluorescent, and natural lighting provide no special obstacles, but do not point an intense or constant light source at the camera because this can blind the RGB sensor.
The depth sensor functions adequately in typical and reduced lighting, although in near darkness there is increased noise in the signal.
The depth sensor reads depth information from reflected light. Objects that are highly reflective (mirrors and shiny metal) or highly absorptive (fluffy and/or dark materials) may not be registered by the depth sensor as successfully as other objects.
for detailed instructions on Setting Up a Kinect Sensor please follow
: https://msdn.microsoft.com/en-us/library/hh855356
I've been involved with a project where I have to install and use a USB GPRS modem on an ARM board (RSC-W910) with Windows CE 6.0 installed.
The modem is the Sierra Wireless product GL6110 (GL61x0) and I need to use it only for data, making HttpWebRequests (TCP) send/receive XML data. Prefered development tool is C# and .Net Framework 3.5.
When the modem is connected via USB to the board, the error message that appears is saying "Unidentified USB Device" which I believe its normal.
Siera Wireless(SW) provides a driver for ARM920, but it failed to install using 'wceload.exe'. The error was "Setup Failed" that I could see on the small LCD screen attached to the board. To install the driver I connect to the board via Telenet and CAB file is stored on SD card.
Am I right to think that the failure to install the driver could be related to the fact that the Win CE image has RAM-based Registry?
If SW does not provide a driver for the modem, could this mean that I have to develop my own driver? or is there a generic driver that I can use instead?
Will I have to create a new Win CE image for the board to support the modem, or is it possible to use code within the C# application to access it?
Any help will be very much appreciated!
Thanks,
Nick
There's no generic driver, no. Sierra modems generally have CE support (I'm not checked this model, but it's likely to work). What you need is:
A Driver DLL, build for ARM and for CE 6.0 or 7.0 (the CE 5.0 driver model differs, so a CE 5.0 driver probably won't work)
The registry entries the device.exe looks for when the device is enumerated
These sometime come in a CAB, sometimes not. Generally I prefer it when they don't but either will work.
If the CAB file fails to install, it's probably because it's marked for some other platform. I'd use something like WinZip or WinRAR to pull it apart, rename the DLL and extract the necessary reg entries (depends on the CAB format how easy/hard this will be).
Generally, though, you need to copy the driver DLL to the \Windows Folder, then apply the registry entries. Then when the device is plugged in, it will read the registry, which will point it to the DLL, which is then loaded. "Unidentified USB device" typically means the registry entries were not found.
This can all be done without rolling a new OS image, though sometimes a new image is simpler than doing the necessary copying at startup, especially if the device is plugged in at boot.
I have a dell desktop pc which has an integrated gpu.
If I add one more gpu over PCIe will I be able to run cuda? Probably yes.
The integrated gpu has its own driver (i915) and I am not sure what will happen with nvidia driver (for the second gpu) alongside.
Is there a special procedure, something to take into account?
edit: forgot to mention that OS is Ubuntu 11.10. sorry
Thanks in advance
UPDATE:
finally there is a problem. I just put the video card gtx 460. I want to have the display on integrated card so as to use the "good" card dedicated to computing. but if i dont plug the monitor cable to gtx I get the following message
System halted! Attention: Unsupported Video Configuration Detected
Action is Required
This computer has an add-in graphics card, but the monitor is plugged
into the integrated video connector. To attach the monitor cable to
the add-in graphics card:
Shut down the computer
Plug the monitor cable into the add-in graphics card connector. This may require a video adapter or video adapter cable. (provided
with the system)
Turn on the computer.
This message should not appear after completing these steps. For more
information or help, please refer to the system documentation.
Please help.
CUDA only supports NVidia GPUs so it won't even see the embedded intel one.
The CUDA startup functions also return the type and capabilities of all the CUDA devices found so you can pick which device to run a task on.
ps. You might want to manually set the app to 'use enhanced/performance graphics' in windows explorer->properties - we have had issues in laptops with Intel+Nvidia optima systems where the app doesn't see the Nvidia GPU by default for some reason
I am relatively new to iOS. I am working developing an app using CoreBluetooth conmunicating with a BLE device. but I failed to test my app on iphone simulator on Mac mini.
My Mac mini has OS Lion,and it has bluetooth4.0.but in iPhone simulator, I cannot open Bluetooth.
The simulator isn't exactly what i would call a good tool since it misses many components of the real device and its behaviour (especially the UI) is way too buggy to give reliable informations.
As for the BT: It could be that your Bluetooth is already used by the OS, so one thing you can try is
$ sudo nvram bluetoothHostControllerSwitchBehavior="never"
and reboot.