Pages: [1]

Author Topic: [Solved]Bad Allocation  (Read 2667 times)

-Archmage-

  • Moderator
  • Dragon
  • ********
  • Posts: 5,887
  • Make it so.
    • View Profile
    • My Website
[Solved]Bad Allocation
« on: 4 March 2012, 08:16:25 »
Made a model from scratch in Blender 2.61. Exported and MG throws me "bad allocation". All faces are triangles. I exported a different model last night with no problem.
« Last Edit: 8 March 2012, 02:01:12 by -Archmage- »
Logged
Egypt Remastered!

Proof: Owner of glest@mail.com

tomreyn

  • MegaGlest Team
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
Re: Bad Allocation
« Reply #1 on: 8 March 2012, 01:46:59 »
Please file a bug report and provide the model file, instructions to reproduce and the general information requested in the sticky thread there.
Logged
atibox: Ryzen 1800X (8 cores @3.6GHz), 32 GB RAM, MSI Radeon RX 580 Gaming X 8G, PCI subsystem ID [1462:3417], (Radeon RX 580 chipset, POLARIS10) @3440x1440; latest stable Ubuntu release, (open source) radeon (amdgpu) / mesa video driver
atibox (old): Core2Quad Q9400 (4 cores @2.66GHz), 8 GB RAM, XFX HD-467X-DDF2, PCI subsystem ID [1682:2931], (Radeon HD 4670, RV730 XT) @1680x1050; latest stable Ubuntu release, (open source) radeon / mesa video driver
notebook: HP envy13d020ng
internet access: VDSL2+

· · · How YOU can contribute to MG · Latest development snapshot · How to build yourself · Megapack techtree · Currently hosted MG games · · ·

-Archmage-

  • Moderator
  • Dragon
  • ********
  • Posts: 5,887
  • Make it so.
    • View Profile
    • My Website
Re: Bad Allocation
« Reply #2 on: 8 March 2012, 02:00:58 »
Sorry guys, this is solved. I had assigned a texture without unwrapping the model in any way. All I had to do was u>unwrap and boom exported fine.
Logged
Egypt Remastered!

Proof: Owner of glest@mail.com

Omega

  • MegaGlest Team
  • Dragon
  • ********
  • Posts: 6,167
  • Professional bug writer
    • View Profile
    • Personal site
Re: [Solved]Bad Allocation
« Reply #3 on: 8 March 2012, 23:39:27 »
Perhaps the export script could be expanded to detect when the model was not unwrapped and a texture has been assigned; notifying the user. Or perhaps the assigned texture should be ignored if the model has not been unwrapped. Or at the most basic level, a more accurate error when a crash occurs because of this reason, to prevent further problems with future users.
Logged
Edit the MegaGlest wiki: http://docs.megaglest.org/

My personal projects: http://github.com/KatrinaHoffert

MightyMic

  • Technician
  • ****
  • Posts: 150
  • To mod, or not to mod...
    • View Profile
Re: [Solved]Bad Allocation
« Reply #4 on: 13 March 2012, 02:22:59 »
I've had this happen to me several times and it's not because of unwrapping. It's because you weren't in object mode and/or didn't have an object selected.

I've noticed that the new script doesn't give the user any warning about that. I remember the script for 2.4 saying that no object was selected... ie no g3d
Logged
Pages: [1]